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/dailygit 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/daily)<a href="https://agentmods.dev/commands/omrikais/cctally/daily"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/daily.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.02416 |
| Opus 5 | $0.00000 | $0.01208 |
| Sonnet 5 | $0.00000 | $0.00483 |
| Haiku 4.5 | $0.00000 | $0.00242 |
Grade A, and why
daily 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
daily
Claude usage grouped by date. Drop-in replacement for ccusage daily,
offline.
Cost coverage: Claude dollar and token totals are transcript-derived lower bounds, not exact
/usagebilling totals.
Canonical form:
cctally claude daily(this flat form remains as an alias).
Synopsis
cctally daily
[-s YYYYMMDD] [-u YYYYMMDD]
[-b] [-o {asc,desc}]
[-m {auto,calculate,display}]
[-i] [-p PATTERN ...] [--project-aliases PAIRS]
[--json]
Options
| Flag | Description |
|---|---|
-s, --since YYYYMMDD |
Filter from date (inclusive). |
-u, --until YYYYMMDD |
Filter until date (inclusive). |
-b, --breakdown |
Show per-model cost breakdown sub-rows. |
-o, --order {asc,desc} |
Sort direction by date (default asc). |
-m, --mode {auto,calculate,display} |
Cost source (drop-in for ccusage daily --mode). auto (default) uses the recorded costUSD from JSONL when present, else computes from embedded pricing — this is the pre-Session-C behavior. calculate always computes from embedded pricing, ignoring any recorded costUSD. display shows the recorded costUSD only, rendering $0.00 when a row has none (ccusage-faithful). Most modern Claude Code JSONL omits costUSD, so under display near-everything reports $0. |
-i, --instances |
Group the report by project (git-root). Renders a section layout — a cyan Project: <label> header per project, that project's daily rows beneath, then one global Total. JSON becomes {projects: {...}, totals}. Drop-in for ccusage daily --instances. |
-p, --project PATTERN |
Filter to projects matching PATTERN — a case-insensitive substring of the project label or its underlying path. Repeatable (-p a -p b), with OR semantics. Without -i, the matches are merged into the normal date-aggregated output (no sections). |
--project-aliases PAIRS |
Comma-separated key=Label pairs overriding project display labels (e.g. lib=Library,cctally-dev=Tracker). The key is matched against a project's label (git-root basename), git-root path, or bucket path. Display-only — the --json projects keys are never aliased. |
--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). |
--json |
Output JSON matching ccusage daily format. Under -i the shape is {projects: {...}, totals} (see Project axis). |
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 · 167 lines · 0 tokens per session scan A 542c8239a35d
daily 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 2,416 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.
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.