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/five-hour-blocksgit 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/five-hour-blocks)<a href="https://agentmods.dev/commands/omrikais/cctally/five-hour-blocks"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/five-hour-blocks.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.02062 |
| Opus 5 | $0.00000 | $0.01031 |
| Sonnet 5 | $0.00000 | $0.00412 |
| Haiku 4.5 | $0.00000 | $0.00206 |
Grade A, and why
five-hour-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 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
five-hour-blocks
List API-anchored 5-hour blocks with rollup totals plus 7d-drift columns.
Cost coverage: Stored Claude block costs are transcript-derived lower bounds, not exact
/usagebilling totals.
Which 5h command?
blocksis the ccusage-compatible per-window view (includes~-prefixed heuristic rows when no recorded reset covers a window);five-hour-blocks(this page) is the API-anchored analytics view with model/project rollups and 7d drift;five-hour-breakdowndrills into per-percent milestones inside one block.
Synopsis
cctally five-hour-blocks
[-s YYYYMMDD] [-u YYYYMMDD]
[--breakdown {model,project}]
[-m {auto,calculate,display}]
[--json] [--no-color] [--tz TZ]
Purpose
Analytics view on the five_hour_blocks table populated by record-usage
each tick. Distinct from cctally blocks (the upstream-parity drop-in that
also shows heuristic-anchored windows): five-hour-blocks is API-anchored
only, and adds 7d-drift columns plus a ⚡ reset-crossing marker.
Options
| Flag | Description |
|---|---|
-s, --since YYYYMMDD |
Filter from date (inclusive). |
-u, --until YYYYMMDD |
Filter until date (inclusive). |
--breakdown {model,project} |
Add per-model OR per-project rollup-child rows under each parent block (single value, not multi). |
-m, --mode {auto,calculate,display} |
Accepted as a no-op for surface parity with the sibling cctally blocks --mode. Unlike blocks/daily/etc. — which recompute per-entry cost from session_entries at query time and so honor the mode — five-hour-blocks reports the authoritative materialized five_hour_blocks.total_cost_usd, computed at record-time (always auto semantics) by _compute_block_totals. There is no query-time per-entry cost path to re-source, so the flag changes nothing. Output is byte-identical across auto/calculate/display. |
--json |
Emit camelCase JSON (schemaVersion: 1). |
--no-color |
Disable ANSI color (currently a no-op — table is plain text). |
--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). |
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 · 165 lines · 0 tokens per session scan A 9a1d5dc015f5
five-hour-blocks 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,062 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.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.