harness-deepseek-harness / rfcs
AGENTS.md2 starsChanged 40 days agoMITView on GitHub
The RFCs under this tree are durable proposals and decisions written by agents: they preserve rationale, alternatives, consequences, and required verification. Follow the documentation standard and the RFC rules. Every new RFC triggers a supersession check. Search the active tree for older RFCs covering the same decision or mechanism, classify any full or partial supersession with archiving-rfcs, and archive every qualifying implemented triplet in the same PR. Keep partial supersessions active and cross-linked. Files under archived/ are frozen historical snapshots:…
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.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/rfcs/archived/AGENTS.mdAGENTS.md
- .agents/rfcs/implemented/AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- archiving-rfcsSkill
- documentingSkill
- editing-proseSkill
- finding-simplificationsSkill
- merging-stacked-prsSkill
- pushingSkill
- reviewingSkill
- translating-docsSkill
- trimming-cot-leakageSkill
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Every new RFC triggers a supersession check: Search the active tree for older RFCs covering the same decision or mechanism, classify any …
≈ “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
AGENTS.md — RFCs
The RFCs under this tree are durable proposals and decisions written by agents: they preserve rationale, alternatives, consequences, and required verification. Follow the documentation standard and the RFC rules.
Every new RFC triggers a supersession check. Search the active tree for older RFCs covering the same decision or mechanism, classify any full or partial supersession with archiving-rfcs, and archive every qualifying implemented triplet in the same PR. Keep partial supersessions active and cross-linked.
Files under archived/ are frozen historical snapshots: never edit them or treat them as current authority.
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.

