owner-operator
AGENTS.md8 starsChanged 44 days agoMITView on GitHub
This folder is the single home for behavior knowledge. Code, README, and prompts point here; they do not restate. - Every page starts with routing frontmatter. title, a one-line summary, and read_when triggers let a reader or agent pick the right page without reading bodies. The summary says what the page is; read_when alone owns when to read it. - One page per surface. A page owns its surface's behavior; overlapping content merges or points. - Point at in-code contracts…
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 repository75 other files it gives its agents.
- AGENTS.mdAGENTS.md
- workspace/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-mattSkill
- codebase-designSkill
- code-reviewSkill
- diagnosing-bugsSkill
- domain-modelingSkill
- gh-searchSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- implementSkill
- improve-codebase-architectureSkill
- prototypeSkill
- pstack-architectSkill
- pstack-arenaSkill
- pstack-automate-meSkill
- pstack-blast-radiusSkill
- pstack-broSkill
- pstack-create-verification-skillSkill
- pstack-figure-it-outSkill
- pstack-howSkill
- pstack-interrogateSkill
- pstack-maintain-verification-skillSkill
- pstack-make-bot-uiSkill
- pstack-no-commentsSkill
- pstack-poteto-modeSkill
- pstack-principle-attack-the-premiseSkill
- pstack-principle-boundary-disciplineSkill
- pstack-principle-build-the-leverSkill
- pstack-principle-encode-lessons-in-structureSkill
- pstack-principle-exhaust-the-design-spaceSkill
- pstack-principle-experience-firstSkill
- pstack-principle-fix-root-causesSkill
- pstack-principle-foundational-thinkingSkill
- pstack-principle-guard-the-context-windowSkill
- pstack-principle-laziness-protocolSkill
- pstack-principle-make-operations-idempotentSkill
- pstack-principle-migrate-callers-then-delete-legacy-apisSkill
- pstack-principle-minimize-reader-loadSkill
- pstack-principle-model-the-domainSkill
- pstack-principle-never-block-on-the-humanSkill
- pstack-principle-outcome-oriented-executionSkill
- pstack-principle-prove-it-worksSkill
- pstack-principle-redesign-from-first-principlesSkill
- pstack-principle-separate-before-serializing-shared-stateSkill
- pstack-principle-sequence-verifiable-unitsSkill
- pstack-principle-subtract-before-you-addSkill
- pstack-principle-test-behavior-not-implementationSkill
- pstack-principle-type-system-disciplineSkill
- pstack-recallSkill
- pstack-reflectSkill
- pstack-setup-pstackSkill
- pstack-show-me-your-workSkill
- pstackSkill
- pstack-swarmSkill
- pstack-tddSkill
- pstack-teachSkill
- The first 60 shown.
The file
We split this AGENTS.md into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Write only the current contract: Before saving, ask: what context am I assuming, what code change would falsify this silently, and where …
≈ “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
Docs
This folder is the single home for behavior knowledge. Code, README, and prompts point here; they do not restate.
- Every page starts with routing frontmatter.
title, a one-linesummary, andread_whentriggers let a reader or agent pick the right page without reading bodies. The summary says what the page is;read_whenalone owns when to read it. - One page per surface. A page owns its surface's behavior; overlapping content merges or points.
- Point at in-code contracts instead of restating them. Catalogs, schema docs, and flag parsers document themselves; pages link to them.
- Write only the current contract. Before saving, ask: what context am I assuming, what code change would falsify this silently, and where else have I already said this?
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.

