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/hexsprite/claude-agents-md/agents-mdgit clone --depth 1 https://github.com/hexsprite/claude-agents-mdWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/hexsprite/claude-agents-md/agents-md)<a href="https://agentmods.dev/instructions/hexsprite/claude-agents-md/agents-md"><img src="https://agentmods.dev/badge/instructions/hexsprite/claude-agents-md/agents-md.svg" alt="Measured on agentmods" height="20"></a>What 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.01304 | $0.01304 |
| Opus 5 | $0.00652 | $0.00652 |
| Sonnet 5 | $0.00261 | $0.00261 |
| Haiku 4.5 | $0.00130 | $0.00130 |
Grade A, and why
claude-agents-md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
agents-md — Agent Instructions
Claude Code plugin that loads AGENTS.md files so cross-tool project instructions
(Cursor, Codex, Windsurf, Continue.dev) work in Claude Code, which natively reads
only CLAUDE.md. This repo dogfoods its own feature: this file is the source of
truth; CLAUDE.md is generated/gitignored, never committed.
Layout
hooks/scan-agents-md.sh— the hook: findAGENTS.md, link/inject asCLAUDE.md, dedupe per session.hooks/hooks.json— registers the hook onSessionStart+UserPromptSubmit..claude-plugin/plugin.json— plugin manifest.tests/— Bun PTY tests.scan-script.test.tsis pure script unit tests (no API);session-start.test.ts/file-changed.test.tsspawn a real Claude session (~60s, burns credits).
Dev
bun install
bun test # all
bun test tests/scan-script.test.ts # fast, no API
Conventions
- Hook is POSIX-ish bash; keep it dependency-light and fast — it runs on every
UserPromptSubmit. - Runtime knobs are
CLAUDE_AGENTS_MD_*env vars (see README). - Any bug fix ships with a regression test in
tests/scan-script.test.ts.
Branches
main— v2 (Bun-preload VFS mode) in progress; replaces the symlink hook as default.v1— symlink/inject hook release line (maintenance).
Beads Issue Tracker
This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --claim # Claim work
bd close <id> # Complete work
Rules
- Use
bdfor ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists - Run
bd primefor detailed command reference and session close protocol - Use
bd rememberfor persistent knowledge — do NOT use MEMORY.md files
Architecture in one line: issues live in a local Dolt DB; sync uses refs/dolt/data on your git remote; .beads/issues.jsonl is a passive export. See https://github.com/gastownhall/beads/blob/main/docs/SYNC_CONCEPTS.md for details and anti-patterns.
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.
- 4d ago First seen · 114 lines · 1,304 tokens per session scan A 077356d46ee8
claude-agents-md AGENTS.md is an instructions file published in the GitHub repository hexsprite/claude-agents-md (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,304 tokens to every session, about $0.0065 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-31.
Other instructions, from other repositories
superpowers-zh CLAUDE.md
Claude Code instructions for jnMetaCode/superpowers-zh, covering superpowers — 贡献者指南, 如果你是 ai agent, pull request 要求, 我们不会接受的内容 and 第三方依赖.
spec-kit-zh AGENTS.md
AGENTS.md instructions for loulanyue/spec-kit-zh, covering agents.md, about spec kit and specify, general practices, adding new agent support and current supported agents.
Meta_Kim CLAUDE.md
Claude Code instructions for KimYx0207/Meta_Kim, covering metakim for claude code, fast read, what this repository is, claude code's role and canonical vs runtime files.
nopua AGENTS.md
Instructions for wuji-labs/nopua, covering nopua · codex 入仓规则, 一 · 项目定位, 二 · 起手必读, 三 · 工程与研究纪律 and 四 · 对外署名.
Atomic-Spec AGENTS.md
Instructions for Chappygo-OS/Atomic-Spec, covering agents.md — adding a new ai agent to atomic spec, about atomic spec and the atomicspec cli, general practices, adding new agent support and current supported agents.
decantr CLAUDE.md
Instructions for decantr-ai/decantr, covering claude.md -- decantr, project, packages, apps and terminology.