red-green
AGENTS.md4 starsChanged 14 days agoMITView on GitHub
Every file in this repository is written in English: code, comments, docs, tickets, specs and commit messages. Sessions with the user may be held in any language; the conversation's language never leaks into files. .scratch/ is git-ignored working material (drafts, specs, tickets). Nothing in it is a permanent source of truth; it was current only when the work was implemented. Verify against the code and docs/ before relying on it. See docs/agents/commits.md. Local markdown under .scratch/<feature>/. See docs/agents/issue-tracker.md. Default five…
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 32,671 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.
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
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
- Distinctive: line 5
Every file in this repository is written in English: code, comments, docs, tickets, specs and commit messages.
- Very specific: line 23
Default five roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) as Status: lines.
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 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.
Files
red-green agent rules
Language
Every file in this repository is written in English: code, comments, docs, tickets, specs and commit messages. Sessions with the user may be held in any language; the conversation's language never leaks into files.
Scratch
.scratch/ is git-ignored working material (drafts, specs, tickets). Nothing in it is a permanent source of truth; it was current only when the work was implemented. Verify against the code and docs/ before relying on it.
Commit messages
See docs/agents/commits.md.
Agent skills
Issue tracker
Local markdown under .scratch/<feature>/. See docs/agents/issue-tracker.md.
Triage labels
Default five roles (needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix) as Status: lines. See docs/agents/triage-labels.md.
Development process
An idea goes grilling → draft spec → prototype → spec → tickets → a session per ticket. Which steps a change takes, and each step's rules: docs/agents/work-process/README.md.
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.

