Borrowing it
Nothing to install: this file belongs to jwchoi-kr/claude-code-usage-per-project. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jwchoi-kr/claude-code-usage-per-project/main/CLAUDE.mdgit clone --depth 1 https://github.com/jwchoi-kr/claude-code-usage-per-projectWrote 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/jwchoi-kr/claude-code-usage-per-project/claude-md)<a href="https://agentmods.dev/instructions/jwchoi-kr/claude-code-usage-per-project/claude-md"><img src="https://agentmods.dev/badge/instructions/jwchoi-kr/claude-code-usage-per-project/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/jwchoi-kr/claude-code-usage-per-project/claude-md"><img src="https://agentmods.dev/badge/instructions/jwchoi-kr/claude-code-usage-per-project/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.02083 | $0.02083 |
| Opus 5.5 | $0.00833 | $0.00833 |
| Sonnet 5.5 | $0.00417 | $0.00417 |
| Haiku 4.5 | $0.00208 | $0.00208 |
Grade A, and why
claude-code-usage-per-project 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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — claude-code-usage-per-project (ccupp)
What this project is
A Claude Code status line + usage tracker. ccupp/cli.py is a thin entry point: main()
dispatches by argv/TTY to one of six modes, each living in its own module:
- Status line — bare
ccupppiped from Claude Code'sstatusLinehook (stdin is not a TTY);main()reads JSON from stdin and delegates rendering toccupp/status_line.py, which prints a 2-line HUD - Usage report — bare
ccupprun in a terminal (TTY);ccupp/report.pyprints a per-session table for the current project - Daily breakdown —
ccupp --daily;ccupp/daily.pyprints the current project's usage grouped by local calendar day - Model breakdown —
ccupp --model;ccupp/model.pyprints the current project's usage grouped by model - All-projects comparison —
ccupp --all;ccupp/all.pyprints a per-project comparison table across every tracked project - Export —
ccupp --export;ccupp/export.pywritesPROMPTS.md
Modes 2–4 are the same current-project scope sliced on a different axis: by session, by day, by model. The --daily and --model modes recompute from the raw transcripts (the per-session snapshots don't carry per-day or per-model splits), reusing the shared aggregate_by_day / aggregate_by_model helpers in ccupp/core.py.
Each user-facing mode is its own module. ccupp/core.py holds only what is shared
across modes (data analysis, persistence, shared formatters). ccupp/status_line.py
holds status-line presentation. Keep mode-specific logic out of ccupp/core.py.
File structure
ccupp/
__init__.py Package marker
__main__.py `python -m ccupp` entry point
cli.py main() dispatcher + install command
status_line.py Status line rendering (2-line HUD)
core.py Shared utilities, data analysis, persistence, table renderer
report.py Terminal usage report — current project (TTY mode)
daily.py Per-day usage breakdown — current project (--daily)
model.py Per-model usage breakdown — current project (--model)
all.py All-projects comparison report (--all)
export.py Prompt extraction and Markdown export (--export)
tests/
__init__.py Package marker
test_cli.py Tests for cli.py (dispatch + install)
test_status_line.py Tests for status_line.py
test_core.py Tests for core.py
test_report.py Tests for report.py
test_daily.py Tests for daily.py
test_model.py Tests for model.py
test_all.py Tests for all.py
test_export.py Tests for export.py
docs/ Historical planning/spec docs — treat as context only
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.
- 2mo ago First seen · 96 lines · 2,083 tokens per session scan A f906e004c4cb
claude-code-usage-per-project CLAUDE.md is an instructions file published in the GitHub repository jwchoi-kr/claude-code-usage-per-project (5 stars, last pushed 5mo ago), licensed MIT. It adds 2,083 tokens to every session, about $0.0083 per session on Opus 5.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
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.