anthropic-watch
AGENTS.md1 starsChanged 7 months agoMITView on GitHub
anthropic-watch — Monitors public Anthropic and community sources daily for changes and publishes structured feeds.
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 repository18 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- agent-routingSkill
- backend-conventionsSkill
- claude-md-maintenanceSkill
- coding-principlesSkill
- context-managementSkill
- coordinator-modeSkill
- frontend-design-systemSkill
- git-conventionsSkill
- memory-architectureSkill
- planning-with-filesSkill
- project-patternsSkill
- prompt-engineeringSkill
- review-and-handoffSkill
- security-checklistSkill
- subagent-usageSkill
- testingSkill
- verificationSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
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 20
Follow existing patterns in the codebase
- Distinctive: line 22
Read source files before modifying them
- Distinctive: line 23
Ask if ambiguous, do not guess
- Distinctive: line 35
Never invent features not in the specification
≈ “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
anthropic-watch — Monitors public Anthropic and community sources daily for changes and publishes structured feeds.
Tech Stack
- Node.js 20+, plain JavaScript (no TypeScript, no build step)
Build & Test Commands
# Node.js
npm test # Run tests
npx eslint . # Lint
npx prettier --write . # FormatCode Conventions
- Follow existing patterns in the codebase
- Test before committing
- Read source files before modifying them
- Ask if ambiguous, do not guess
Project Structure
src/— Source codetest/— Test filesdocs/— Documentation
Key Principles
- Source of truth: docs/spec/SPEC.md
- One task at a time, verify each before moving on
- Never invent features not in the specification
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.

