skills
AGENTS.md179 starsChanged 9 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,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 repository10 other files it gives its agents.
- appstore-intelSkill
- creative-directionSkill
- design-tokensSkill
- hn-searchSkill
- motion-design-patternsSkill
- privacy-cardsSkill
- producthuntSkill
- recursive-improvementSkill
- trademark-searchSkill
- visual-qaSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 2 are common, 4 are distinctive, and 0 are very specific to this project.
≈2
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
- Common: line 3
No hardcoded API keys, secrets, or tokens
- Distinctive: line 6
All API routes must have error handling (try/catch, proper status codes)
- Distinctive: line 8
No TODO comments without context or linked issues
- Distinctive: line 9
Verify env vars are documented if new ones are added
- Distinctive: line 10
Check for SQL injection / unsanitized user input
- Common: line 11
No secrets or PII in comments or variable names
≈ “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
Review guidelines
- No hardcoded API keys, secrets, or tokens
- No
console.login production code (use proper logging or remove) - No
anytypes in TypeScript — use proper types - All API routes must have error handling (try/catch, proper status codes)
- Database queries must handle errors gracefully
- No TODO comments without context or linked issues
- Verify env vars are documented if new ones are added
- Check for SQL injection / unsanitized user input
- No secrets or PII in comments or variable names
- Imports should be used — flag dead imports
- Functions over 50 lines should be flagged for refactoring consideration
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.