sentinel
AGENTS.md0 starsChanged 9 days agoMITView on GitHub
Sentinel holds shared rules and skills for coding agents. Read README.md first. - rules/AGENTS.md holds the rules. The installers copy it into each host file without a change. Edit the rules only when the user asks. - tools/install and tools/install.ps1 must write the same bytes. Change both in the same commit. - upstream/lock.json lists the files that come from other repositories. After you edit one of these files, run node tools/upstream.mjs --sync. Import a new revision with node tools/upstream.mjs --update.…
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 repository24 other files it gives its agents.
- rules/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- babysit-prSkill
- beast-uiSkill
- cleanupSkill
- councilSkill
- doc-viewSkill
- featuremapSkill
- file-prSkill
- frontend-designSkill
- full-sendSkill
- full-stopSkill
- impeccableSkill
- leaving-pr-commentsSkill
- modernizeSkill
- no-commentsSkill
- patrolSkill
- sol-loopSkill
- statechartSkill
- technical-writingSkill
- tldrSkill
- untangleSkill
- verify-prSkill
- whySkill
The file
We split this AGENTS.md into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 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.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 11
After you edit one of these files, run node tools/upstream.mjs --sync.
- Very specific: line 12
Import a new revision with node tools/upstream.mjs --update.
- Very specific: line 13
Run make test before you push.
≈ “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
Work on Sentinel
Sentinel holds shared rules and skills for coding agents. Read README.md
first.
rules/AGENTS.mdholds the rules. The installers copy it into each host file without a change. Edit the rules only when the user asks.tools/installandtools/install.ps1must write the same bytes. Change both in the same commit.upstream/lock.jsonlists the files that come from other repositories. After you edit one of these files, runnode tools/upstream.mjs --sync. Import a new revision withnode tools/upstream.mjs --update.- Run
make testbefore you push. CI also runs the tests on macOS and Windows.
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.