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/phuryn/claude-usage/agents-mdgit clone --depth 1 https://github.com/phuryn/claude-usageWhat 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.04058 | $0.04058 |
| Opus 5 | $0.02029 | $0.02029 |
| Sonnet 5 | $0.00812 | $0.00812 |
| Haiku 4.5 | $0.00406 | $0.00406 |
Grade A, and why
claude-usage 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 3d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for any coding agent (Codex, Claude Code, etc.) working on this repository.
Naming note. This project analyzes Claude Code's local usage logs, so "Claude Code" below always refers to that product (the source of the JSONL data) — not to the agent reading this file. The agent working on the codebase is referred to as "the coding agent" or just "you".
Project shape
Three Python files, stdlib only, no pip install step. Python 3.8+.
- scanner.py — parses Claude Code JSONL transcripts into a SQLite DB at
~/.claude/usage.db. - cli.py — terminal commands (
scan/today/week/stats/dashboard). - dashboard.py — single-file
http.serverserving an embedded HTML/JS SPA onlocalhost:8080.
Use python on Windows, python3 on macOS/Linux. Both work the same.
Common commands
python cli.py scan # incremental scan (fast on re-run)
python cli.py today # today's usage by model
python cli.py week # last 7 days, per-day + by-model
python cli.py stats # all-time stats
python cli.py dashboard # scan + open http://localhost:8080
python cli.py dashboard --host 0.0.0.0 --port 9000
python cli.py scan --projects-dir PATH # scan a custom transcripts dir
# or via env vars:
HOST=0.0.0.0 PORT=9000 python cli.py dashboard
python -m unittest discover -s tests -v # full test suite (CI runs this)
python -m unittest tests.test_scanner -v # one file
python -m unittest tests.test_scanner.TestProjectNameFromCwd.test_windows_path # one test
CI (.github/workflows/tests.yml) runs the suite on Python 3.9 / 3.11 / 3.12 against main and PRs.
Architecture
Data flow
~/.claude/projects/**/*.jsonl → scanner.parse_jsonl_file()
~/Library/.../Xcode/... ↓
aggregate_sessions() → upsert_sessions() + insert_turns()
↓
~/.claude/usage.db (SQLite)
↓
cli.py queries ←──────────→ dashboard.py /api/data
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.
- 3d ago First seen · 170 lines · 4,058 tokens per session scan A c78d72e54ef4
claude-usage AGENTS.md is an instructions file published in the GitHub repository phuryn/claude-usage (2,185 stars, last pushed 1mo ago), licensed MIT. It adds 4,058 tokens to every session, about $0.0203 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
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.