thea-software
llms.txt3 starsChanged 13 days agoMITView on GitHub
Rules and build checks for AI coding agents. First reply: act; ask for a task only if none was given. With headron, skip this reply; ["port", "<file>"] before edits; ["verify"] before done. No shell: CHAT.md, skill first. headron <verb>, in a clone python scripts/atlas.py <verb> (atlas.py port <file>), or MCP (read-only). Exit code is the verdict; JSON: tools/atlas-output.schema.json.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- HLIntel/Headronword for word, first seen Nov 1, 2026
Other versions1 project uses a version of this.
Word for word · 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.
In this repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- headronSkill
- headronSkill
- landSkill
- rekickSkill
- syncSkill
- run-workflowSkill
The file
We split this llms.txt into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
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
- Very specific: line 44
use: run headron gate <file> and the commands it prints.
- Very specific: line 49
report: run failures <id> --draft '<text>', then skills/headron/SKILL.md.
≈ “Common” is an estimate: at least 1 in 5 of the 3,592 llms.txt 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.
Files
# Headron Software by HLIntel LLC (contract v3.62.0) > Rules and build checks for AI coding agents. <!-- GENERATED from atlas.yaml by `atlas.py index --write`; do not edit. --> - **Is:** a CLI and rule contract for AI coding agents. Each changed file maps to the checks it owes; the commit hook refuses one that fails to parse or type-check, `headron verify` runs the rest. - **Is not:** a coding agent, model, test framework, or proof code is correct. A check that cannot run reports SKIP or NOT RUN, never a pass; the hook lets that commit through. - **Needs:** Python >=3.11, pyyaml, defusedxml. No account or key. A package install fetches its matching release from GitHub on first run. - **`headron init` writes:** AGENTS.md, CLAUDE.md, .mcp.json, .codex/config.toml, .git/hooks/pre-commit. An existing hook moves to `pre-commit.legacy` and still runs; `headron enforce uninstall` restores it. - **Mind API:** hosted, paid, needs a key; plans a declared change. The command line works without it. **First reply**: act; ask for a task only if none was given. With `headron`, skip this reply; `["port", "<file>"]` before edits; `["verify"]` before done. No shell: [CHAT.md](CHAT.md), skill first. ## Verbs `headron <verb>`, in a clone `python scripts/atlas.py <verb>` (`atlas.py port <file>`), or MCP (read-only). Exit code is the verdict; JSON: `tools/atlas-output.schema.json`. - `intake [<prompt>]`: a prompt as a task: file, role, change class, gates, next; or the questions it lacks - `resume`: where interrupted work stands, and the one next action - `port [<target>]`: route, tier, gates, lessons, next commands for a file or tree - `find <query>`: search: embeddings, prefixes, pointers - `route <path>`: pack, card, manifest, lane and the rule that resolved a path - `gate <path> [<gate>]`: the one command a gate runs for a file - `plan <path>`: the gates a task and change class need for a path - `steps <path>`: ordered plan for one runtime, entry to return - `pipeline <path>`: one file end to end: ingest, classify, verify, exit - `shell [<cmd>]`: refuse shell whose verdict or effect differs from what its writer reads - `failures [<id>]`: mistakes agents made here, each with its guard - `landed <branch>`: is every branch change in the base? Ask before deleting - `check`: the whole contract - `verify`: every done gate once: PASS, FAIL or NOT RUN, by exit code - `doctor`: local prerequisites; packprobe checks language tools - `commands`: every command and instrument, as text or JSON ## Records - `.agent/bootstrap.json`: this entry as JSON · `.agent/facts.json`: every published figure - `AGENTS.md`/`CLAUDE.md`: agent runtimes; rules for changing Headron itself · `CHAT.md`: a chat with no shell - `route <file>`: which of the 40 packs governs it; then read its `tools.yaml` ## When asked to use, install, open, run, pull, report - **use**: run `headron gate <file>` and the commands it prints; `headron enforce install` makes every commit prove itself. - **install**: README's quickstart; in a clone, `python -m pip install --require-hashes -r scripts/requirements.lock.txt`. - **open**: load only your runtime's entry file, then `headron port <path>`; never read the tree breadth-first. - **run**: `headron verify` for your change; `headron check` for the whole contract. - **pull**: pin a release tag, never main; to update a clone, `git pull --ff-only` then `headron check`. - **report**: run `failures <id> --draft '<text>'`, then `skills/headron/SKILL.md`. ## Files - [MODEL.md](MODEL.md): operating model; read when routed - [atlas.yaml](atlas.yaml): single source of truth: routes, invariants, gates, profiles, policy - [docs/INDEX.md](docs/INDEX.md): every document - [SECURITY.md](SECURITY.md): security policy and measured platform controls
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
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.

