agents
AGENTS.md0 starsChanged 4 months agoMITView on GitHub
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,843 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 repository17 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- branch-safelySkill
- deployment-decisionsSkill
- deploySkill
- deploy-vercelSkill
- deploy-vpsSkill
- documentationSkill
- e2e-testingSkill
- feature-testingSkill
- monitoringSkill
- orchestrateSkill
- quality-reviewSkill
- requirements-gatheringSkill
- solution-designSkill
- task-breakdownSkill
- ui-uxSkill
- unit-testingSkill
The file
We split this AGENTS.md into the rules it gives an agent
5 rules. About 1 is common, 3 are distinctive, and 1 is very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈3
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 3
Keep portable workflow behavior in core/.
- Distinctive: line 4
Keep adapters, skills, playbooks, templates, and durable workflow policy under version control.
- Distinctive: line 5
Do not commit transient installed workflow state or failure logs.
- Distinctive: line 6
Do not pin a model or provider in toolkit adapters.
- Common: line 7
Keep risk-based permission rules aligned across core roles, adapters, skills, and installation paths.
≈ “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
Toolkit Conventions
- Keep portable workflow behavior in
core/; adapters are hand-maintained tool wrappers, not automatic translation. - Keep adapters, skills, playbooks, templates, and durable workflow policy under version control.
- Do not commit transient installed workflow state or failure logs.
- Do not pin a model or provider in toolkit adapters.
- Keep risk-based permission rules aligned across core roles, adapters, skills, and installation paths. Never weaken protected-file approval or secret redaction rules.
- Known local build, test, and dev commands are allowed by default. Package installation, publishing, destructive, remote, and secret-related commands ask first.
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.