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/pricing-checkgit 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/pricing-check)<a href="https://agentmods.dev/commands/omrikais/cctally/pricing-check"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/pricing-check.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.02627 |
| Opus 5 | $0.00000 | $0.01314 |
| Sonnet 5 | $0.00000 | $0.00525 |
| Haiku 4.5 | $0.00000 | $0.00263 |
Grade A, and why
pricing-check 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 4d 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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
pricing-check
Detect whether cctally's embedded model pricing
(CLAUDE_MODEL_PRICING / CODEX_MODEL_PRICING) has gone stale or is
missing a model. cctally prices every session locally from these embedded
tables; an unrecognized Claude model silently contributes $0 and an
unrecognized Codex model is approximated via the gpt-5 fallback. This
command surfaces those gaps proactively instead of waiting for someone to
reconcile by hand.
It is the network-aware counterpart to the offline
doctor pricing.coverage check, and the entry point for the
weekly pricing-freshness CI workflow.
Synopsis
cctally pricing-check [--json] [--offline]
Purpose
Three independently-degrading legs:
- Coverage (offline, all-history) — models in your cached session data
(
cache.db) that cctally cannot price exactly: Claude models priced at$0(unpriced) or Codex models approximated via thegpt-5fallback (fallback). The Codex ingest sentinelunknownis excluded: it means the rollout did not retain a model identifier, so it is not a model that can be added to the pricing table. No network; a read-only scan over the cache. - Drift (network, LiteLLM) — embedded price values vs the LiteLLM pricing snapshot. Direction-aware (see below) and allowlist-suppressed.
- Existence (network, Anthropic
/v1/models) — vendor models the API offers that our table lacks. Anthropic-only and maintainer-local (needs a Claude OAuth bearer); see the asymmetry + caveat sections.
The tool detects; a human applies. It never auto-edits the pricing tables — the verified-against-vendor discipline stays.
Options
| Flag | Effect |
|---|---|
--json |
Emit the machine-readable payload (schemaVersion: 1) to stdout. CI consumes this. |
--offline |
Run the coverage leg only. The drift + existence legs are skipped (no network). |
Exit codes
Exit code and status are orthogonal: the exit code reports whether you
must act; status reports whether the check was complete.
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.
- 4d ago First seen · 208 lines · 0 tokens per session scan A 6be56953da9e
pricing-check is a command published in the GitHub repository omrikais/cctally (5 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,627 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.