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/weeklygit 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.00922 |
| Opus 5 | $0.00000 | $0.00461 |
| Sonnet 5 | $0.00000 | $0.00184 |
| Haiku 4.5 | $0.00000 | $0.00092 |
Grade A, and why
weekly 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
weekly
Claude usage grouped by subscription week (anchored to --resets-at),
with Used % and $/1% columns daily/monthly don't have.
Cost coverage: Claude dollar and token totals are transcript-derived lower bounds, not exact
/usagebilling totals.
Canonical form:
cctally claude weekly(this flat form remains as an alias).
Synopsis
cctally weekly
[-s YYYYMMDD] [-u YYYYMMDD]
[-b] [-o {asc,desc}]
[-m {auto,calculate,display}]
[--json]
Purpose
The "what did each subscription week cost me" view. Unlike calendar-week
groupings, the boundaries here align with Anthropic's actual quota window
so Used % and $/1% are directly meaningful.
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 week (default asc). |
-m, --mode {auto,calculate,display} |
Cost source (drop-in for ccusage weekly --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. The pre-snapshot extrapolation tail carries no entries, so its weeks contribute $0 regardless of mode. |
--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. |
Examples
cctally weekly
cctally weekly --since 20260101
cctally weekly --breakdown
cctally weekly --json
cctally weekly --order desc
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 · 81 lines · 0 tokens per session scan A 3ecb5ef9df5e
weekly 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 922 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.
constitution
Create or update the project constitution from interactive or provided principle inputs.