A local report of Claude Code spending grouped by Monday-based week, with the newest weeks first. Claude Code is a coding assistant, and the report reads its existing local session logs.

Use it to review spending over roughly the last 12 weeks or filter the weekly totals by a project or branch name.

It shows weekly costs without contacting an API, needing a key, or adding prompts or network delay.

by-week — Command by RoninForge

Install

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.

agentmods

npx agentmods add commands/roninforge/claude-code-cost/by-week

Clone the repo

git clone --depth 1 https://github.com/RoninForge/claude-code-cost

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 413 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 88% copy Near-identical to another mod in the catalogue.

Token cost

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.00041	$0.00413
Opus 5	$0.00020	$0.00206
Sonnet 5	$0.00008	$0.00083
Haiku 4.5	$0.00004	$0.00041

Measured 2d ago against content hash 027b8d38f4d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

by-week 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.

Origin

This is a copy

88% identical to by-day — 10 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.

commands/by-week.md · 25 lines

What it actually says

Show the user their Claude Code spend broken down by week.

Run exactly this command with the Bash tool, passing the user's arguments through verbatim:

node "${CLAUDE_PLUGIN_ROOT}/scripts/cost.mjs" --mode by-week $ARGUMENTS

Then present the command's stdout to the user VERBATIM inside a fenced code block. Do not reformat the table, do not add columns, do not re-sort rows, and do not convert it to Markdown. Do not editorialize or add commentary about the numbers unless the user explicitly asks for analysis.

Notes for you (the model), not for the user:

Output is a WEEK OF SPEND table covering the last ~12 weeks, newest week first, with a TOTAL footer. Each row is labelled with that week's Monday (UTC). Only weeks with spend appear.
The script reads only the local JSONL session logs under ~/.claude/projects. It never touches API traffic: zero key, zero prompts, zero latency. This view always reads the raw logs directly (it does not use budgetclaw, which has no per-date data).
A first non-flag argument is a case-insensitive substring filter on project or branch name, scoping the weekly totals to that project/branch (for example /claude-code-cost:by-week roninforge).
--json makes it emit a JSON array of {period, spend} instead of the table.
If the output ends with a "Note:" line about unpriced models, keep it.
If the script prints "No Claude Code spend tracked yet." or "No Claude Code session logs found ...", relay that message as-is.

Changes

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 · 25 lines · 41 tokens per session scan A 027b8d38f4d7

Subscribe to this mod's changes

by-week is a command published in the GitHub repository RoninForge/claude-code-cost (2 stars, last pushed 25d ago), licensed MIT. It adds 41 tokens to every session and 413 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to by-day, differing in 10 lines, and is treated as a copy.

Backend and APIs Code review Git and workflow anthropic claude-code claude-code-plugin cli cost-tracking developer-tools

by-week

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

release

dashboard

branch

export

pricing

stats