agentleFS
Sign inStart free
HLIntelHLIntel/thea-software/AGENTS.md

thea-software

AGENTS.md3 starsChanged 13 days agoMITView on GitHub

GENERATED by python scripts/atlas.py index --write; atlas.py check fails on any hand edit. It comes from atlas.yaml, VERSION and the tree: change the declaration, not this file. Never read this repository breadth-first. Ask where to go, then load only what the answer names. Plug in: python scripts/atlas.py port <file|dir|.> --frame agent: route, tier, gates, lessons, next steps. Hooks: shell headron shell --json "<cmd>" · edit headron port <file> --line · done headron verify. Asked to use, install, open, run, pull,…

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 1

    1. HLIntel/Headron★ 3100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • 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 repository9 other files it gives its agents.

The file

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

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Never read this repository breadth-first: Ask where to go, then load only what the answer names.

    line 8
  2. Very specific:

    Every limit names its closer: All 95 instruments carry proves, does_not_prove and closed_by.

    line 30
  3. Distinctive:

    A change ends when the artifact parses: Every tracked source and JSON file must parse.

    line 34

≈ “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

AGENTS.md — Headron Software, contract v3.62.0

GENERATED by python scripts/atlas.py index --write; atlas.py check fails on any hand edit. It comes from atlas.yaml, VERSION and the tree: change the declaration, not this file.

Ask, do not read

Never read this repository breadth-first. Ask where to go, then load only what the answer names.

Plug in: python scripts/atlas.py port <file|dir|.> --frame agent: route, tier, gates, lessons, next steps. Hooks: shell headron shell --json "<cmd>" · edit headron port <file> --line · done headron verify.

python scripts/atlas.py gate  <path> <gate>    # ONE command: cheapest answer, most accurate
python scripts/atlas.py plan  <path> --task <task> --change <class> [--modifier <m>] --json
python scripts/atlas.py check                  # exit code IS the verdict; doctor: can it run here

Asked to use, install, open, run, pull, report this repository? llms.txt → When asked to. Directed into a role? headron role. Picking up interrupted work? headron resume. --json records are frozen in tools/atlas-output.schema.json: depend on those ids.

Rules that fail the build

  1. No count typed into prose. Generate it, or name the instrument that prints it.
  2. No calendar date. Stamp a claim with its contract version; only an external project's own date-shaped version (atlas.yaml/external_versions) is exempt.
  3. No tool name in prose. Tools live in languages/<route>/tools.yaml; documents name gates.
  4. Refuse rather than invent. none is a real answer; a parser that picks a winner on ambiguous input is worse than one that errors.
  5. Every limit names its closer. All 95 instruments carry proves, does_not_prove and closed_by; an empty closer fails.
  6. Never raise a cap to fit your code. code_shape and context_policy ratchets only fall: split the function or shrink the entry path.
  7. A change ends when the artifact parses. Every tracked source and JSON file must parse; that check runs first.
  8. A control with no enforcer is refused. Controls, sandbox rows and gates each name their deciding function (atlas.yaml/agent_policy).

Mistakes made here before, by an agent

Each RECURRED here: once is a bug, twice a rule. Learn the shapes; they return in other files.

  • a_check_proven_on_one_shape_of_input — a verified command, and a hook that suddenly rejects good code; a passing MCP probe, and a client that cannot connect
  • …and 123 more: headron failures

Before you claim a change is done

Pick the change class (source_change, api_change, dependency_change, security_sensitive, concurrency_change, performance_change, retrieval_change) and satisfy its gates, then verify on the exit code, never on output:

python scripts/verify.py    # PASS / FAIL / NOT RUN per gate; exit 0 only if every gate passed

It runs verification_policy/done_set and prints each gate. Both suites plant a real defect per rule and assert their own case counts: new rule, new planted defect. Land with python scripts/branchstate.py --land; a bare push of a lane is refused.

Where to put what

Repeated fact: atlas.yaml plus a generated block. Language tool: its pack's tools.yaml. New rule: its own *_errors() and planted defect. Example: examples/, and it must run.

Runtime notes

  • One body for every runtime, pointed at and never copied: CLAUDE.md routes here, Hermes reads .agent/bootstrap.json, a bare model llms.txt. Adapter: models/<runtime>/README.md; MODEL.md.

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