Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/commands/omrikais/cctally/percent-breakdown)<a href="https://agentmods.dev/commands/omrikais/cctally/percent-breakdown"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/percent-breakdown.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.1 | $0.00000 | $0.00703 |
| Opus 5 | $0.00000 | $0.00351 |
| Sonnet 5 | $0.00000 | $0.00141 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
percent-breakdown 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 5d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
percent-breakdown
Per-percent cumulative and marginal cost milestones for a single week.
Cost coverage: Stored Claude milestone costs are transcript-derived lower bounds, not exact
/usagebilling totals.
Synopsis
cctally percent-breakdown
[--week-start YYYY-MM-DD]
[--week-start-name {monday,…,sunday}]
[--json]
Purpose
When record-usage sees a snapshot crossing an integer percent threshold,
it writes a row to percent_milestones. This command renders those rows
for a chosen week so you can see exactly when each percent was reached and
what it cost incrementally.
Options
| Flag | Description |
|---|---|
--week-start YYYY-MM-DD |
Week start date. Defaults to the current week. |
--week-start-name |
Week-start day used when no explicit date or usage data is available. |
--tz TZ |
Display timezone for this call (local, utc, or IANA, e.g. America/New_York). Overrides config display.tz. See Display timezone for the full contract (parsing scope, JSON UTC invariant). |
--json |
Machine-readable JSON output. |
Examples
cctally percent-breakdown
cctally percent-breakdown --week-start 2026-03-20
cctally percent-breakdown --json
Notes
- Output includes the 5-hour percent at the moment of each crossing
(added by A1 — the
five_hour_percent_at_crossingcolumn onpercent_milestones). Useful for correlating big cost jumps with short-window usage spikes. - Only milestones recorded by
record-usageshow up — if your status line wasn't running for part of the week, you'll see gaps, and they cannot be retroactively reconstructed. report --detailcalls into the same renderer for the current week.- After an in-place weekly credit, this view has a gap it cannot fill
(issue #213). A partial credit lowers the reported weekly percentage
without re-anchoring the week, and
percent_milestonesis forward-only: no new row is recorded until usage climbs back above the pre-credit peak. So every percent between the post-credit level and that peak is missing here, and so is the spend attributed to it. The rows that are present are correct; the ones that are absent were never recorded, and no command reconstructs them. Anything built on these rows — the alert next step that offerspercent-breakdown,report --detail, and the dashboard's per-percent view — inherits the same gap.cctally record-creditdocuments the credit model itself.
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.
- 5d ago First seen · 70 lines · 0 tokens per session scan A 0711f9c9482c
percent-breakdown is a command published in the GitHub repository omrikais/cctally (5 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 703 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
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…
archive-ledger
../../../shared/commands/archive-ledger.md.
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.