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/omrikais/cctally/budgetgit clone --depth 1 https://github.com/omrikais/cctallyWrote 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/budget)<a href="https://agentmods.dev/commands/omrikais/cctally/budget"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/budget.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.07171 |
| Opus 5 | $0.00000 | $0.03585 |
| Sonnet 5 | $0.00000 | $0.01434 |
| Haiku 4.5 | $0.00000 | $0.00717 |
Grade A, and why
budget 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.
How it starts
The opening of the file, as written. The whole thing — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cctally budget
Track spend against a budget, per vendor (Claude and/or Codex) over a
configurable calendar period. cctally budget shows spend, pace, projected
end-of-period, and a verdict (ok / warn / over); cctally budget set <amount> and cctally budget unset manage the budget. When a budget is set and
alerts are enabled, a desktop alert fires once per crossed threshold as actual
spend passes it (see Alert behavior).
Claude cost coverage: Claude spend is a transcript-derived lower bound, not an exact
/usagebilling total. Codex accounting is unaffected.
The Claude budget defaults to the subscription week (the original v1 behavior) but can run over a calendar week or calendar month instead. A separate Codex (OpenAI) budget tracks Codex's actual API dollars over a calendar week or month — Codex has no Anthropic subscription week, so a Codex budget is calendar-period only. The two budgets are independent: configure either, both, or neither. There is no combined cross-vendor cap (Claude is equivalent-$, Codex is actual-$ — they are not summed).
budget is a cctally-original command (not a ccusage drop-in), so there is
no claude budget / codex budget subgroup form — the flat cctally budget
is the only surface.
Subcommands
cctally budget— status report (Claude block, then the Codex block when configured, then per-project).cctally budget set <amount>— set the Claude budget to<amount>USD (a positive finite number). Confirms with the resolved budget + period + alert state.cctally budget set <amount> --vendor codex— set the Codex budget. Codex requires a calendar period (--period calendar-weekorcalendar-month; defaultcalendar-month).cctally budget set <amount> --period {calendar-week,calendar-month,subscription-week}— set the Claude budget's period. Omitting--periodpreserves the stored period (or the per-vendor default on first create).cctally budget unset— clear the Claude budget amount (period + alert thresholds are preserved for the nextset).cctally budget unset --vendor codex— remove the Codex budget entirely.
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 · 487 lines · 0 tokens per session scan A 6b20ae29bdfd
budget is a command published in the GitHub repository omrikais/cctally (5 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 7,171 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
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
scan
Scan AWS account for cost optimization.
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
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…