five-hour-breakdown

five-hour-breakdown is a command for Claude Code from omrikais/cctally. It costs 0 tokens per session (1,918 once invoked), scanned A, original, Apache-2.0.

A command that shows cumulative and additional costs at each percentage milestone within one five-hour usage block. The block is anchored to a recorded API reset time.

In plain words
What is it for?
Use it to inspect one five-hour block in detail, either as a terminal report or JSON output, with optional time-zone and block-selection settings.
Why use it?
It shows when usage milestones were reached and how much each step added, instead of only showing the final total.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md). Also seen: mentions CLAUDE.md.

Not installable on its own: it reads a path above its own folder, which only exists inside its repository. The line is [transcript-derived lower bounds](../claude-cost-coverage.md), not exact.

Install

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.

Made for: Claude Code.

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.

agentmods badge for five-hour-breakdown

README.md
[![agentmods](https://agentmods.dev/badge/commands/omrikais/cctally/five-hour-breakdown.svg)](https://agentmods.dev/commands/omrikais/cctally/five-hour-breakdown)
Your own site
<a href="https://agentmods.dev/commands/omrikais/cctally/five-hour-breakdown"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/five-hour-breakdown.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,918 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01918
Opus 5 $0.00000 $0.00959
Sonnet 5 $0.00000 $0.00384
Haiku 4.5 $0.00000 $0.00192

Measured 6d ago against content hash bfd04995c809, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

five-hour-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 6d 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.

docs/commands/five-hour-breakdown.md · 180 lines

How it starts

The opening of the file, as written. The whole thing — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.

five-hour-breakdown

Per-percent cumulative + marginal cost milestones inside a single API-anchored 5-hour block. Mirror of percent-breakdown for the 5h axis.

Cost coverage: Stored Claude milestone costs are transcript-derived lower bounds, not exact /usage billing totals.

Which 5h command? blocks is the ccusage-compatible per-window view (includes ~-prefixed heuristic rows when no recorded reset covers a window); five-hour-blocks is the API-anchored analytics view with model/project rollups and 7d drift; five-hour-breakdown (this page) drills into per-percent milestones inside one block.

Synopsis

cctally five-hour-breakdown
    [--block-start ISO8601 | --ago N]
    [--json] [--no-color] [--tz TZ]

Purpose

When record-usage sees a 5h-window snapshot crossing an integer percent threshold, it writes a row to five_hour_milestones. This command renders those rows for one block so you can see exactly when each percent was reached and what it cost incrementally — the same lens as percent-breakdown, but scoped to a 5h window instead of a week.

Block selector

Flag Behavior
(none — default) Current/most-recent API-anchored block (active or last-closed).
--block-start <iso> Explicit. Accepts ISO 8601 with offset (2026-04-30T19:30:00Z, 2026-04-30T22:30:00+03:00) or naive (2026-04-30T19:30). Naive selectors are interpreted as UTC. Date-only inputs (2026-04-30) are rejected with exit 2.
--ago N Relative; 0 = current, 1 = previous, …. Mutually exclusive with --block-start.

--tz affects display only; it does NOT shift selector parsing.

The selector resolves through _canonical_5h_window_key, so any timestamp within the same 10-minute floor as the actual block matches correctly.

Options

Flag Description
--block-start ISO8601 Explicit selector (see above).
--ago N Relative selector (see above).
--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). Note: --block-start selector parsing is not display-tz-shifted (see callout in "Block selector" above).

Read the full file on GitHub · 180 lines

Changes

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.

  1. 6d ago First seen · 180 lines · 0 tokens per session scan A bfd04995c809

Subscribe to this mod's changes

five-hour-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 1,918 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.