vanguard-frontier-agentic / catalog
AGENTS.md23 starsChanged 4 months agoApache-2.0View on GitHub
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 33,315 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 repository15 other files it gives its agents.
- agents/AGENTS.mdAGENTS.md
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- mcp/AGENTS.mdAGENTS.md
- rules/AGENTS.mdAGENTS.md
- schemas/AGENTS.mdAGENTS.md
- skills/AGENTS.mdAGENTS.md
- templates/AGENTS.mdAGENTS.md
- tests/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- agentic-delegationSkill
- definition-of-doneSkill
- model-registry-refreshSkill
- pr-babysitSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Keep catalog paths relative to repo root.
- Distinctive: line 17
Keep IDs unique across all catalog files.
- Distinctive: line 18
Update catalog and adjacent metadata together.
- Very specific: line 20
Run npm run validate before finishing.
≈ “Common” is an estimate: at least 1 in 5 of the 42,283 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
Purpose
- Store machine-readable marketplace indexes and integrity manifests.
Files
skills.json→ cataloged skill entries.agents.json→ cataloged agent entries.rules.json→ cataloged rule entries.mcp-references.json→ cataloged MCP reference entries.workflows.json→ delegation workflows discovered in.claude/workflows/(generated).skill-manifest.json→ SHA-256 integrity map for cataloged skills.index.json→ catalog entrypoint.
Rules
- Keep catalog paths relative to repo root.
- Keep IDs unique across all catalog files.
- Update catalog and adjacent metadata together.
- Regenerate
skill-manifest.jsonafter intentional skill file edits. - Run
npm run validatebefore finishing.
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.

