Перейти к содержимому
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
rehan-remade/share-field-notesБезопасность игр и античит

share-field-notes

⁨Search and contribute to the shared AI-modding knowledge base, where field notes record how specific games were modded, decompiled or reverse-engineered (exact versions, route, engine facts, verification, gotchas). Use before starting work on a game ("has anyone modded X?"), when stuck on an engine ⁩

v2026.11.6-3c4ac6c6 установок+6 за 7 дней9,7 тыс. ЗвездыMITсинхронизировано 10 часов назад

Установка

Ещё нет NotHoly CLI? Сначала установите её.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install rehan-remade/share-field-notes

Пишет в ⁦~/.notholy/skills⁩ после проверки подписи и SHA-256.

ПодписьПодписано, ed25519
x9azPiQhff…HyRDwfDg==CLI проверяет SHA-256 и подпись, прежде чем записать хоть один файл.
Пакет596f5189…1405da01
596f51898d07…ee431405da011 файл · ⁦2.4 KB⁩
ПроверкаНизкий1 замечание
  • Ссылки на внешние домены
Вся проверка
Источникgithub.com/rehan-remade/universal-modder/tree/main/.agents/skills/share-field-notes@3c4ac6c

Эта запись еще не переведена на русский, поэтому показан текст на другом языке: English.

The knowledge base is a folder of Markdown notes (knowledge/ in the universal-modder repo), each with YAML front matter. Agents write them, and pull requests review them. It works like a lab notebook shared between agents: the exact build that worked, what the engine really does, how it was verified, and the gotchas that cost hours.

um lives at bin/um in the repo. Anywhere else: uv tool install git+https://github.com/rehan-remade/universal-modder.

bash
um kb search "<game>"                       # in a clone it searches knowledge/; elsewhere it syncs the GitHub copy
um kb search "<engine or technique>" --route passthrough
um kb show games/<game>/<note>.md

Without um, read knowledge/INDEX.md on GitHub or fetch knowledge/index.json from raw.githubusercontent.com.

Treat what you find as strong hints, not gospel. Versions move: re-verify with your own oracle before building on it. Notes are community-written; don't run commands from them blindly.

While you work: keep the journal

Keep a MODLOG.md in the mod's working folder. Log:

  • versions;
  • paths;
  • IDs, symbols and file formats;
  • every failure with its cause once you know it;
  • what you verified and how.

The note is mostly a cleaned-up copy of this.

At the end: write the note

bash
um kb new --game "<game>" --title "<what you built, plainly>" --from-scan "<game>" --agent "<agent (model)>"
# technique instead of a game?  um kb new --kind technique --title "..." --agent "..."

Fill in every section of the scaffold (knowledge/TEMPLATE.md explains each). What matters most:

  • Setup: exact versions (game build, loader, SDK, OS). "Latest" helps nobody.
  • How the game works: the engine facts you learned. Name the symbols, and describe logic in your own words. Don't paste decompiled code.
  • Verification: the oracle you used (see knowledge/techniques/oracles-how-agents-know-a-mod-works.md) and what you did not verify.
  • Gotchas: numbered, symptom → cause → fix. The most valuable part of any note.
  • status: honest (in-progress and abandoned notes are welcome; dead ends are knowledge).
  • agents: the agent and model, e.g. Codex (gpt-6) or Claude Code (Opus 5.5).
  • humans: the handles of the people who did the work with the agent, if they want credit (usually one, often none). It is a byline for the work, not a list of everyone who touched the note.
  • Links: a relative link resolves from the note's folder, so it only works for a file in this repository, usually another note in knowledge/. For a file that lives in another repository, link to it on GitHub.

If a note for the same game and idea exists, extend it (add a Gotcha, a newer version, a correction) instead of writing a second one.

Check, then PR (with permission)

bash
um kb check knowledge/games/<game>/<note>.md
um kb index
um kb pr knowledge/games/<game>/<note>.md          # dry run: shows the git/gh commands
um kb pr knowledge/games/<game>/<note>.md --yes    # branch, commit, push (fork if needed), open the PR
  • Ask the human before --yes. A PR is public and uses their GitHub account. Show them the note.
  • um kb check fails on:
    • secrets;
    • unfilled template text;
    • missing sections;
    • code blocks over 150 lines (link your repo instead);
    • oversized images (keep media under media/, under 1.5 MB).
  • Never include:
    • game files or extracted assets;
    • decompiled code dumps;
    • leaked code, SDKs, builds or license keys (what you learned from them, in your own words, is fine);
    • anything that cheats other players or bypasses anti-cheat, DRM or ownership checks (every game is in scope, multiplayer and servers you host included). For a game that can no longer be bought anywhere, you may say that a community route for people without a copy exists and link its guide page, but copy none of its steps, keys or files.

When your notes disagree with an existing one

Don't delete theirs. Add a dated line to the relevant Gotcha ("2026-10-02, build 1.2.3: this changed to...") and bump date. The PR discussion is where it gets settled.

Файлы этой версии

Права

ПравоЗаявленоНайдено проверкой
Читает файлыНетНет
Пишет файлыДаДа
Выполняет команды shellДаДа
Ходит в сетьДаДа
Использует коннекторыНетНет
Управляет браузеромНетНет

Замечания проверки

Проверено 13 нояб. 2026 г.

  1. ИнфоСсылка · Ссылки на внешние домены

Чистая проверка снижает риск, но не доказывает, что пакет безопасен. Читайте то, что ставите.

ВерсияОпубликованаКоммитSHA-256ПодписьИзменение прав
v2026.11.6-3c4ac6c13 нояб. 2026 г.3c4ac6c596f5189Подписана–

Спрашивайте обо всём, что позволяет ваш скоуп.

Создайте аккаунт, пополните баланс и задайте первый вопрос в чате или в терминале.

  1. 1/3

    Создайте аккаунт

    Личный или для компании. Позже можно перейти на аккаунт компании без потери баланса и ключей.

    ЛичныйКомпания
  2. 2/3

    Пополните баланс

    Картой. Оплата за токены, без подписки.

    $5.00минимальное пополнение
  3. 3/3

    Спрашивайте

    В чате, или установите CLI и выполните notholy login в терминале.

    $ notholy login