registery
AGENTS.md1 starsChanged 8 months agoMITView on GitHub
- Reads credentials
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.
In this repository25 other files it gives its agents.
- architect-reviewSkill
- brainstormingSkill
- changelog-writerSkill
- dispatching-parallel-agentsSkill
- documentation-writerSkill
- executing-plansSkill
- fastapiSkill
- makefileSkill
- pgvector-semantic-searchSkill
- postgres-patternsSkill
- python-patternsSkill
- python-testingSkill
- requesting-code-reviewSkill
- ruffSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- task-doc-navigatorSkill
- test-driven-developmentSkill
- tySkill
- using-git-worktreesSkill
- using-superpowersSkill
- uvSkill
- verification-before-completionSkill
- writing-plansSkill
- writing-skillsSkill
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
- Very specific: line 2
Do not inspect local .env files unless the user explicitly asks.
- Distinctive: line 3
When executing an attached plan, do not edit the plan file.
≈ “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
Learned User Preferences
- Do not inspect local
.envfiles unless the user explicitly asks; use example files, docs, or ask the user to confirm values instead. - When executing an attached plan, do not edit the plan file; use existing todos when provided, mark progress as work begins, and continue through the listed todos.
Learned Workspace Facts
- Observability should stay dormant by default unless explicitly reactivated; avoid reintroducing local Grafana/Prometheus/Loki or enabling OTEL/Grafana Cloud automatically.
- The root/status page should avoid
healthz/readyzendpoint labels and duplicate DB rows; readiness already covers DB, and the public spec button copy should beopenAPI.
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.