zetetic-team-subagents
AGENTS.md8 starsChanged 57 days agoMITView on GitHub
The plugin that defines the agents, skills, commands, hooks and rules every other repository runs under. Python tooling, Markdown agent definitions. This file is deliberately short: the host loads what it needs on demand. Everything that used to be here is in docs/agent-guidance.md (repo-specific constraints, etiquette). Read it before any non-trivial change. - Any .md under agents/ is parsed as an agent definition. Non-agent documentation goes in rules/, never in agents/. - The zetetic spine is generated, not hand-edited: scripts/generate-spine.py…
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 repository16 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- boundary-designSkill
- causal-auditSkill
- decision-bias-checkSkill
- estimationSkill
- evidence-synthesisSkill
- experience-and-transmissionSkill
- failure-forensicsSkill
- formal-correctnessSkill
- measurement-disciplineSkill
- narrative-sensemakingSkill
- normative-designSkill
- problem-reframingSkill
- representation-and-possibilitySkill
- structure-discoverySkill
- systems-leverageSkill
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 8
Read it before any non-trivial change.
≈ “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
zetetic-team-subagents
The plugin that defines the agents, skills, commands, hooks and rules every other repository runs under. Python tooling, Markdown agent definitions.
This file is deliberately short: the host loads what it needs on demand. Everything that
used to be here is in docs/agent-guidance.md (repo-specific constraints, etiquette).
Read it before any non-trivial change.
Commands
bash tests/run-all.sh # full test suite
ZETETIC_PROFILE=strict bash tools/zetetic-checker.sh --staged
bash tools/doc-count-check.sh
bash tools/doc-command-check.shNon-negotiables
- Any
.mdunderagents/is parsed as an agent definition. Non-agent documentation goes inrules/, never inagents/. - The zetetic spine is generated, not hand-edited:
scripts/generate-spine.pyinjects the<zetetic-spine>block into every anchor-bearing agent. Edit the generator, never the outputs. - This clone is live-mounted as the installed plugin: edits take effect immediately in
running sessions. Never edit
~/.Codex/plugins/cache; change it here.
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.