agent-context-kit
AGENTS.md1 starsChanged 3 months agoMITView on GitHub
Before starting any task, run /directives context "<task description>" to load the relevant conventions for that task. Do not proceed without doing this first. Before starting an operational task (deploy, generate an access token, compile, rotate credentials, run a database migration, ...), run /how-tos context "<task description>" to load the relevant procedure. Do not proceed without doing this first. Before writing a new script or tool, or doing something manually that could be scripted, run /scripts context "<task description>" to…
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,843 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- context-refactorSkill
- directivesSkill
- how-tosSkill
- scriptsSkill
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
- Very specific: line 4
Before starting any task, run /directives context "<task description>" to load the relevant conventions for that task.
- Very specific: line 9
Before starting an operational task (deploy, generate an access token, compile, rotate credentials, run a database migration, ...), run …
- Very specific: line 15
Before writing a new script or tool, or doing something manually that could be scripted, run /scripts context "<task description>" to check …
≈ “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
Directives
Before starting any task, run /directives context "<task description>" to load the relevant
conventions for that task. Do not proceed without doing this first.
How-Tos
Before starting an operational task (deploy, generate an access token, compile, rotate
credentials, run a database migration, ...), run /how-tos context "<task description>" to load
the relevant procedure. Do not proceed without doing this first.
Scripts
Before writing a new script or tool, or doing something manually that could be scripted, run
/scripts context "<task description>" to check whether one already exists. Prefer running an
existing script over reimplementing the same logic inline.
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.