agentleFS
Sign inStart free
f0909172434f0909172434/rigorgraph/AGENTS.md

rigorgraph

AGENTS.md1 starsChanged 4 months agoMITView on GitHub

Before reporting completion, run: Also build the frontend and validate the plugin and all four skills. Static checks alone do not establish that the CLI, report, wheel, or GitHub Action works.

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository4 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep v1 local-first: no telemetry, hosted database, built-in paid model API, editable report, or MCP server.

    line 7
  2. Very specific:

    Every core message ID must exist in en, zh-TW, zh-CN, and ja.

    line 18
  3. Distinctive:

    Keep machine keys, enum values, error codes, IDs, paths, and hashes in English.

    line 19
  4. Distinctive:

    Do not automatically translate user-authored claims, quotations, formulas, or evidence.

    line 20
  5. Very specific:

    Run python scripts/validate_locales.py after changing any user-facing string.

    line 21
  6. Distinctive:

    Before reporting completion, run:

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

RigorGraph agent guidance

Product boundary

  • Preserve the distinction between proof, literature support, numerical evidence, benchmark evidence, and open questions.
  • VERIFIED is a workflow status, not absolute truth, formal certification, peer review, or expert consensus.
  • Keep v1 local-first: no telemetry, hosted database, built-in paid model API, editable report, or MCP server.

Source of truth

  • Python source: src/rigorgraph/.
  • Frontend source: frontend/; regenerate src/rigorgraph/viewer/index.html with npm.cmd run build on Windows or npm run build elsewhere. Do not hand-edit the generated HTML.
  • Schemas: generate with python scripts/export_schemas.py; do not hand-edit generated schema JSON.
  • Canonical skill content: skills/; plugin manifest: .codex-plugin/plugin.json.

Internationalization

  • Every core message ID must exist in en, zh-TW, zh-CN, and ja.
  • Keep machine keys, enum values, error codes, IDs, paths, and hashes in English.
  • Do not automatically translate user-authored claims, quotations, formulas, or evidence.
  • Run python scripts/validate_locales.py after changing any user-facing string.

Verification

Before reporting completion, run:

python -m pytest
python -m ruff check .
python scripts/export_schemas.py --check
python scripts/release_check.py --full

Also build the frontend and validate the plugin and all four skills. Static checks alone do not establish that the CLI, report, wheel, or GitHub Action works.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free