dirban
AGENTS.md0 starsChanged 2 days 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 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 repository3 other files it gives its agents.
- code-reviewSkill
- copywritingSkill
- task-managementSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 0 are distinctive, and 4 are 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.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 4
Mise as Source of Truth: All runtime versions (bun, node) MUST be managed through mise and declared in mise.toml.
- Very specific: line 8
No Unpinned Execution: Never use npx or bunx. They pull and execute latest unpinned, unaudited packages from the registry.
- Very specific: line 9
Explicit Pinned Dependencies: All tools, linters, compilers, and bundlers must be explicitly declared and pinned in package.json …
- Very specific: line 10
Approved Execution: Use bun run <script>, bun run <bin>, or ./node_modules/.bin/<bin>.
≈ “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
Workspace Axioms & Operational Rules
1. Runtime Version Management
- Mise as Source of Truth: All runtime versions (
bun,node) MUST be managed throughmiseand declared inmise.toml. - Execute commands via
mise exec -- <command>(or within an active mise environment).
2. Package Management & Security
- No Unpinned Execution: Never use
npxorbunx. They pull and execute latest unpinned, unaudited packages from the registry. - Explicit Pinned Dependencies: All tools, linters, compilers, and bundlers must be explicitly declared and pinned in
package.json(dependenciesordevDependencies) with a committed lockfile (bun.lock). - Approved Execution: Use
bun run <script>,bun run <bin>, or./node_modules/.bin/<bin>.
3. Git & Branching Axiom
- Trunk-Based Development: The single source of truth is
main. All work uses short-lived task branches (task/<id>-<slug>) originating frommainand integrating directly back intomain. Long-lived staging/release branches are forbidden. See docs/concepts/git-workflow.md.
4. Standards & Architecture References
- UI Iconography Standards: .agents/rules/ui-icons.md
- Package Management Rule: .agents/rules/package-management.md
- TypeScript Standards: .agents/rules/typescript.md
- Testing Standards: .agents/rules/tests.md
- Documentation Standards: .agents/rules/document.md
- File & Directory Naming: .agents/rules/file-naming.md
- Agent Instructions Guide: .agents/rules/agent-instructions.md
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.

