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/spences10/claude-code-analytics/claude-mdgit clone --depth 1 https://github.com/spences10/claude-code-analyticsWhat 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.00132 | $0.00132 |
| Opus 5 | $0.00066 | $0.00066 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
claude-code-analytics 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.
What it actually says
Unbreakable rules:
- Don't rush, THINK things through first
- snake case for function and variables names
- Kebab case for file names
- Don't over engineer simple solutions
- Always use pnpm for package management
At the start of every session, load up on context from @docs/README.md and @TODO.md
Database path is ~/.claude/claude-code-analytics.db there is no
database in the root of this project.
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 · 16 lines · 132 tokens per session scan A 850f0dcd213d
claude-code-analytics CLAUDE.md is an instructions file published in the GitHub repository spences10/claude-code-analytics (11 stars, last pushed 6d ago), licensed MIT. It adds 132 tokens to every session, about $0.0007 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
databasement CLAUDE.md
Claude Code instructions for David-Crty/databasement, covering claude.md, project overview, development commands, setup and installation and running the application.
claude-code-statusline AGENTS.md
Instructions for ilia-pluzhnikov/claude-code-statusline, covering claude-code-statusline, project shape, rules for contributors (and ai agents), editing this file and testing.
codemark GEMINI.md
Instructions for DanielCardonaRojas/codemark, covering development workflow and debugging with the tui logging system.
agent-tools AGENTS.md
Instructions for kairyou/agent-tools, covering agent instructions, build and test, layout, settled decisions and docs.
rekal AGENTS.md
Instructions for janbjorge/rekal, covering rekal: agent instructions, what this project is, architecture, key rules and re-expansion bar.
rekal CLAUDE.md
Instructions for janbjorge/rekal, a project described as: Long-term memory for LLMs. MCP server backed by hybrid search in a single SQLite file.