by-day

by-day is a command for coding agents from RoninForge/claude-code-cost. It costs 40 tokens per session (399 once invoked), scanned A, original, MIT.

A local report of Claude Code spending grouped by calendar day, with the newest days first. Claude Code is a coding assistant, and the report reads its existing local session logs.

In plain words
What is it for?
Use it to inspect spending over roughly the last month or filter the daily totals by a project or branch name.
Why use it?
It shows recent daily costs without contacting an API, needing a key, or adding prompts or network delay.

Command

Installs and runs on its own, but its text points at files inside its plugin — anything it tells you to read at a ${CLAUDE_PLUGIN_ROOT} path is only there once the plugin is installed. Installing the plugin gets both.

Part of the claude-code-cost plugin — 5 commands shipped together

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-day
Clone the repo
git clone --depth 1 https://github.com/RoninForge/claude-code-cost

Or install claude-code-cost, the plugin that ships this one along with the rest of its 5 commands.

Wrote 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.

agentmods badge for by-day

README.md
[![agentmods](https://agentmods.dev/badge/commands/roninforge/claude-code-cost/by-day.svg)](https://agentmods.dev/commands/roninforge/claude-code-cost/by-day)
Your own site
<a href="https://agentmods.dev/commands/roninforge/claude-code-cost/by-day"><img src="https://agentmods.dev/badge/commands/roninforge/claude-code-cost/by-day.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 399 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.00399
Opus 5 $0.00020 $0.00199
Sonnet 5 $0.00008 $0.00080
Haiku 4.5 $0.00004 $0.00040

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

Security

Grade A, and why

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

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

  • by-month — 89% identical, 10 lines differ
  • by-week — 88% identical, 10 lines differ
commands/by-day.md · 25 lines

What it actually says

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

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

node "${CLAUDE_PLUGIN_ROOT}/scripts/cost.mjs" --mode by-day $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 DATE SPEND table covering the last ~30 days, newest day first, with a TOTAL footer. Only days 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 daily totals to that project/branch (for example /claude-code-cost:by-day 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.

  1. 3d ago First seen · 25 lines · 40 tokens per session scan A fe53a86bad38

Subscribe to this mod's changes

by-day is a command published in the GitHub repository RoninForge/claude-code-cost (2 stars, last pushed 27d ago), licensed MIT. It adds 40 tokens to every session and 399 once invoked, about $0.0002 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-31.