duo
AGENTS.md22 starsChanged 41 days agoMITView on GitHub
The in-app template maker is the authoring surface for every coordination method.
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.
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 6
If the maker cannot express a required behavior, extend the shared template model, validator, executor, and visual controls first.
- Distinctive: line 7
Every shipped template must be recreatable from a new method in the visual maker.
- Distinctive: line 9
Keep host operations as reusable, validated building blocks for mechanical work such as citation checks, ledger updates, ranking, and …
- Distinctive: line 10
When adding a template capability, verify visual authoring, saved-definition round trips, and execution.
≈ “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.
Files
Template-first coordination
The in-app template maker is the authoring surface for every coordination method.
- Make behavior changes in the template whenever its existing building blocks can express them.
- If the maker cannot express a required behavior, extend the shared template model, validator, executor, and visual controls first. Then compose the behavior in the template.
- Every shipped template must be recreatable from a new method in the visual maker. Copying a built-in or editing JSON cannot be the only way to obtain a capability.
- Expose the full customization available to shipped templates, including stage prompts, settings, workflow branches, response contracts, roles, routing, memory, and run controls. Do not offer controls the executor ignores.
- Keep host operations as reusable, validated building blocks for mechanical work such as citation checks, ledger updates, ranking, and workspace isolation. Stage order and completion policy belong in template data; do not inject hidden stages from a report or finalizer.
- When adding a template capability, verify visual authoring, saved-definition round trips, and execution. Keep existing user changes intact.
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.