Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/bgreenwell/dotagents/agents-mdgit clone --depth 1 https://github.com/bgreenwell/dotagentsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00185 | $0.00185 |
| Opus 5 | $0.00093 | $0.00093 |
| Sonnet 5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
dotagents AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
AGENTS.md
Project purpose
You are maintaining dotagents, a draft, vendor-neutral convention for organizing project context for AI coding agents.
Prioritize clarity, interoperability, safety, and consistency between the proposal and its checked-in examples.
Context routing
- Before changing documentation or examples: READ
CONTRIBUTING.md. - When checking release or version history: READ
CHANGELOG.md. - When changing terminology or directory semantics: READ
docs/terminology.md. - When making a structural or naming decision: CONSULT
docs/decisions.md. - When working on an active proposal: CHECK
docs/specs/README.md. - When reviewing the convention: ADOPT
.agents/personas/standards-reviewer.md.
Validation
- After changing this router or routed files, use
.agents/skills/validate-context-routes/SKILL.md.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 21 lines · 185 tokens per session scan A 7f416035ec7b
dotagents AGENTS.md is an instructions file published in the GitHub repository bgreenwell/dotagents (87 stars, last pushed 1mo ago), licensed MIT. It adds 185 tokens to every session, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
cli AGENTS.md
Instructions for konteks/cli, covering agent instructions, project overview, tech stack, repository layout and common commands.
varve CLAUDE.md
Instructions for varve-sh/varve, covering varve, memory tools, rules (always follow) and what actually happens when you call these tools.
skill-everything CLAUDE.md
Instructions for sordi-ai/skill-everything, covering skill-everything, your responsibilities, sub-skill directory, error capture triggers and important.
skill-everything AGENTS.md
Instructions for sordi-ai/skill-everything, covering agents.md, what this project is, sub-skill directory, how to use and important.
engineering-memlog CLAUDE.md
Claude Code instructions for atazifor/engineering-memlog, covering engineering-memlog plugin — agent instructions, how the log gets into your context, search the log yourself when warranted, append a lesson after you work and plugin knobs (env vars).
sleepsweet AGENTS.md
AGENTS.md instructions for SleepSweet/sleepsweet: This project cleans and audits agent memory — we practice what we preach, so keep this file and your own notes about the repo accurate and current.