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/simozampa/clankerchat/claude-mdgit clone --depth 1 https://github.com/simozampa/clankerchatWrote 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/simozampa/clankerchat/claude-md)<a href="https://agentmods.dev/instructions/simozampa/clankerchat/claude-md"><img src="https://agentmods.dev/badge/instructions/simozampa/clankerchat/claude-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.00032 | $0.00032 |
| Opus 5 | $0.00016 | $0.00016 |
| Sonnet 5 | $0.00006 | $0.00006 |
| Haiku 4.5 | $0.00003 | $0.00003 |
Grade A, and why
clankerchat CLAUDE.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 5d 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
clankerchat Development
Preserve concurrent changes, make small Conventional Commits without attribution trailers, and run npm run check before declaring work complete.
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.
- 5d ago First seen · 4 lines · 32 tokens per session scan A 7720c34f02f0
clankerchat CLAUDE.md is an instructions file published in the GitHub repository simozampa/clankerchat (2 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session, about $0.0002 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
adk-java GEMINI.md
Gemini CLI instructions for google/adk-java, covering gemini code assistant context, project overview, building and running, maven commands and development workflow.
open-agents AGENTS.md
AGENTS.md instructions for vercel-labs/open-agents, covering agents.md, quick links, authentication, database & migrations and environment isolation.
solo AGENTS.md
AGENTS.md instructions for solo-agent/solo, covering project testing rules and project service lifecycle rules.
research-os AGENTS.md
Instructions for lxinfei5/research-os, covering researchos — constitution, §0 what this is, §1 directory discipline, §2 half-life (innovation 1) — memory design and §3 behavior pillars (innovations 2–5).
sprawling CLAUDE.md
Instructions for 2youg1/sprawling: See AGENTS.md. It is the whole instruction set for this repository — the loop, what to read first, the five steps of one change, the rules a machine holds, and the language and commit conventions.
axonhub CLAUDE.md
Claude Code instructions for looplj/axonhub: @AGENTS.md read and follow its instructions.