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/beeltec/context-usage-mcp/claude-mdgit clone --depth 1 https://github.com/beeltec/context-usage-mcpWhat 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.00003 | $0.00003 |
| Opus 5 | $0.00002 | $0.00002 |
| Sonnet 5 | $0.00001 | $0.00001 |
| Haiku 4.5 | $0.00000 | $0.00000 |
Grade A, and why
context-usage-mcp 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 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.
This is a copy
100% identical to deepseek-harness CLAUDE.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
AGENTS.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 · 1 lines · 3 tokens per session scan A a54ff182c7e8
context-usage-mcp CLAUDE.md is an instructions file published in the GitHub repository beeltec/context-usage-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 3 tokens to every session, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to deepseek-harness CLAUDE.md, differing in 0 lines, and is treated as a copy.
Other instructions, from other repositories
datalens-dev-mcp AGENTS.md
Instructions for ADIKANT/datalens-dev-mcp, covering agents.md, scope, read order, local material policy and public change hygiene.
printyourduck-mcp AGENTS.md
AGENTS.md instructions for printyourduck/printyourduck-mcp, covering agent guide, product boundary, commands, repo ownership and release truth.
homelab-asset-db-mcp CLAUDE.md
Claude Code instructions for McCavity/homelab-asset-db-mcp, covering homelab-asset-db-mcp — conventions for ai agents, what this project is, key design choices, parser contract and coding conventions.
wikipedia-mcp-server AGENTS.md
AGENTS.md instructions for cyanheads/wikipedia-mcp-server, covering developer protocol, what's next?, core rules, patterns and tool.
wikipedia-mcp-server CLAUDE.md
Claude Code instructions for cyanheads/wikipedia-mcp-server, covering developer protocol, what's next?, core rules, patterns and tool.
mcp-server-excel coverage-prevention-strategy.instructions.md
Instructions for sbroenne/mcp-server-excel, covering generated surface coverage, contract change workflow, required checks and common incomplete changes.