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/blocksgit clone --depth 1 https://github.com/omrikais/cctallyWhat 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.02468 |
| Opus 5 | $0.00000 | $0.01234 |
| Sonnet 5 | $0.00000 | $0.00494 |
| Haiku 4.5 | $0.00000 | $0.00247 |
Grade A, and why
blocks 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
blocks
Claude usage grouped by 5-hour session block.
Cost coverage: Claude dollar and token totals are transcript-derived lower bounds, not exact
/usagebilling totals.
Canonical form:
cctally claude blocks(this flat form remains as an alias).
Which 5h command?
blocks(this page) is the ccusage-compatible per-window view (includes~-prefixed heuristic rows when no recorded reset covers a window);five-hour-blocksis the API-anchored analytics view with model/project rollups and 7d drift;five-hour-breakdowndrills into per-percent milestones inside one block.
cctally blocks aims for parity with ccusage blocks's output shape but
implements two intentional improvements over upstream:
- 5h block boundaries follow Anthropic's
rate_limits.5h.resets_at(10-minute granularity) wherever a recorded snapshot covers the window, not the legacy hour-floor algorithm. A first message at 7:10 PM anchors the block at 7:10, not 7:00. ccusage still usesfloor_to_hour(rust/crates/ccusage/src/blocks.rs:51-54). Windows with no recorded reset fall back to a heuristic start and render as~-prefixed rows that can drift from the real boundary (see Notes). - Duplicate-pair dedup matches ccusage's
should_replace_deduped_entry(rust/crates/ccusage/src/claude_loader.rs:531) — higher-token-total wins,speed-set breaks ties. Fixed in v1.12.0; pre-fix versions kept the streaming-intermediate row and systematically under-counted output tokens on tool-using turns. - Block projection uses the real reset start, not entry-span. cctally
projects
tokens ÷ (now − real reset start) × full 5h window; ccusage usescurrent + (tokens ÷ (last entry − first entry)) × time remaining(projectBlockUsage). cctally's model leverages the API-anchored window start that ccusage only guesses, so theProjected Usagenumbers differ by design. The-abox and the table's PROJECTED footer both reflect this formula.
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.
- 2d ago First seen · 163 lines · 0 tokens per session scan A a57a1e62bbb5
blocks is a command published in the GitHub repository omrikais/cctally (5 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 2,468 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
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.