agent-notes-toolkit
AGENTS.md0 starsChanged 3 months agoMITView on GitHub
This repository ships the Agent Notes mechanism as a portable toolkit and is its own reference user: the .agents/notes tree here is maintained with the toolkit itself, and CI runs the same gates the toolkit publishes.
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,542 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 repository6 other files it gives its agents.
- .agents/notes/AGENTS.mdAGENTS.md
- .agents/notes/archived/AGENTS.mdAGENTS.md
- .agents/notes/implemented/AGENTS.mdAGENTS.md
- archive-notesSkill
- note-workflowSkill
- prose-standardSkill
The file
We split this AGENTS.md into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Every non-trivial change ships with an Agent Note under .agents/notes.
- Very specific: line 9
Before finishing a change, run node lib/cli.js verify and npm test.
≈ “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
AGENTS.md — Agent Notes Toolkit
This repository ships the Agent Notes mechanism as a portable toolkit and is its own reference user: the .agents/notes tree here is maintained with the toolkit itself, and CI runs the same gates the toolkit publishes.
Working in this repository
- Every non-trivial change ships with an Agent Note under
.agents/notes; follow.agents/notes/README.md. - Implemented notes stay current with what actually shipped; archive them per
skills/archive-notes/SKILL.mdwhen they stop guiding work. - Before finishing a change, run
node lib/cli.js verifyandnpm test; both must be green. - The gates live in
gates/, the CLI inlib/cli.js, scaffold templates inscaffold/, maintenance skills inskills/, and the dsh bundle inpackages/dsh-an. Every deliberate difference from the upstreamdeepseek-harnessmechanism is recorded indocs/deviations.md. - Prose follows
skills/prose-standard/SKILL.md: one physical line per paragraph, complete contracts, no reasoning-transcript residue.
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.