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 commands/bhvbhushan/codeledger/dashboardgit clone --depth 1 https://github.com/bhvbhushan/codeledgerWrote 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/commands/bhvbhushan/codeledger/dashboard)<a href="https://agentmods.dev/commands/bhvbhushan/codeledger/dashboard"><img src="https://agentmods.dev/badge/commands/bhvbhushan/codeledger/dashboard.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00120 |
| Opus 5 | $0.00000 | $0.00060 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
dashboard 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.
What it actually says
Start the CodeLedger dashboard by running the following command in the terminal:
npx codeledger dashboard
This opens a local web dashboard at http://localhost:4321 with:
- Overview: total spend, user vs overhead split, daily cost chart, model distribution
- Projects: per-project breakdown with session drill-down
- Agents: per-agent table with user/overhead filtering, click project to see its agents
- Skills: per-skill estimated token usage (~estimated)
The dashboard reads from the same local database as the MCP tools. No data leaves your machine.
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 · 14 lines · 0 tokens per session scan A 386196abffeb
dashboard is a command published in the GitHub repository bhvbhushan/codeledger (9 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 120 tokens. 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 commands, from other repositories
by-project
Claude Code spend per project (branches merged) with today / this week / this month and the last active date, ranked by month spend. Computed locally from the session logs Claude Code already writes. Never touches API traffic; zero key, zero prompts, zero latency.
report
Claude Code spend in USD per project and per git branch (today / this week / this month), computed locally from the session logs Claude Code already writes. Never touches API traffic; zero key, zero prompts, zero latency.
by-day
Claude Code spend grouped by calendar day, dated, most recent first. Computed locally from the session logs Claude Code already writes. Never touches API traffic; zero key, zero prompts, zero latency.
by-week
Claude Code spend grouped by Monday-based week, dated, most recent first. Computed locally from the session logs Claude Code already writes. Never touches API traffic; zero key, zero prompts, zero latency.
by-month
Claude Code spend grouped by calendar month, dated, most recent first. Computed locally from the session logs Claude Code already writes. Never touches API traffic; zero key, zero prompts, zero latency.
learn
Force claude-smart to extract learnings from this session now.