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/sync-weekgit 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.00700 |
| Opus 5 | $0.00000 | $0.00350 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
sync-week 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sync-week
Compute the USD cost for a subscription week and store it in
weekly_cost_snapshots.
Cost coverage: The stored Claude cost is a transcript-derived lower bound, not an exact
/usagebilling total.
Synopsis
cctally sync-week
[--week-start YYYY-MM-DD] [--week-end YYYY-MM-DD]
[--week-start-name {monday,…,sunday}]
[--mode {auto,calculate,display}]
[--offline] [--project PROJECT]
[--json] [--quiet]
Purpose
Walk Claude session JSONLs in the chosen week window, compute total USD
cost from CLAUDE_MODEL_PRICING, and persist a snapshot. report reads
these snapshots to compute $/1%.
Week selection priority
- Explicit
--week-start/--week-end(date based) - Latest
weekly_usage_snapshots.week_start_at/week_end_at(hour-accurate) - Current week from configured week-start rule (
--week-start-name→config.json→monday)
Options
| Flag | Description |
|---|---|
--week-start YYYY-MM-DD |
Explicit week start date. If --week-end is omitted, uses start + 6 days. |
--week-end YYYY-MM-DD |
Explicit inclusive week end (for custom windows). |
--week-start-name |
Week-start day used when explicit/custom boundaries are unavailable. |
--mode {auto,calculate,display} |
Cost calculation mode (default auto). |
--offline |
No-op; pricing data is always embedded. |
--project PROJECT |
Filter cost calc to a single Claude project (cwd). |
--json |
Machine-readable JSON output. |
--quiet |
Suppress human-readable output (no effect with --json). |
Examples
cctally sync-week
cctally sync-week --week-start 2026-02-05 --week-end 2026-02-12
cctally sync-week --mode calculate --offline --json
Notes
sync-weekis idempotent per invocation — calling it twice in a row writes two snapshot rows for the same week.reportreads the latest per-week row.--mode displayreuses the value computed at last--mode calculaterather than recomputing from JSONLs. Use it as a low-cost refresh.- Cost is only stored here; if you change
CLAUDE_MODEL_PRICING, re-runsync-weekto pick up the new rates inweekly_cost_snapshots. (Other commands likedaily/weeklyrecompute on every read and don't need this.)
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 · 73 lines · 0 tokens per session scan A b9623ad0b5fe
sync-week 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 700 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.