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/accountgit 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/account)<a href="https://agentmods.dev/commands/omrikais/cctally/account"><img src="https://agentmods.dev/badge/commands/omrikais/cctally/account.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.03429 |
| Opus 5 | $0.00000 | $0.01715 |
| Sonnet 5 | $0.00000 | $0.00686 |
| Haiku 4.5 | $0.00000 | $0.00343 |
Grade A, and why
account 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cctally account
Inspect the per-provider account registry. cctally observes which Claude or Codex account each usage sample was written under — reading the provider's own on-disk credential state, never any third-party switcher tool — and records milestones, quota, and alerts per account. This subcommand lists the observed accounts, shows one account's identity and attribution summary, and sets a durable friendly label.
Multi-account support is byte-stable: with at most one real account per provider (a legacy unattributed bucket does not count), every default render is identical to a single-account install. Account decoration — labels, extra columns, JSON keys — appears only once a provider has more than one real account, or when you explicitly ask for it (--account, cctally account …).
Usage
cctally account list [--json]
cctally account show <ref> [--json]
cctally account label <ref> <name>
cctally account attribute <ref> --since <iso> [--until <iso>] [--retract] [--yes] [--json]
list
Lists every observed account with its provider, label, email, plan, first/last-seen timestamps, and a live active marker (the account currently logged in per the provider's credential state). --json emits the stamped-first camelCase envelope (schemaVersion: 1) with an accounts array.
show <ref>
Shows one account's identity plus a short attribution summary (how many usage snapshots and percent milestones are stamped to it). --json emits the envelope.
label <ref> <name>
Sets a durable, user-provided label for the account. User labels win over any auto-derived or switcher-imported label (user > switcher > auto) and survive cctally db rebuild --db stats because the rename is journaled.
attribute <ref> --since <iso> [--until <iso>]
Attributes already-recorded Codex quota windows and spend to a known Codex account.
cctally learned to record which account each sample belongs to partway through its life. Everything recorded before that carries the unattributed bucket, and nothing else can move it — so on a multi-account Codex install the whole earlier history stays unattributed permanently. This command lets you state the fact you already know: that a stretch of recorded Codex history belongs to a particular account.
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 · 143 lines · 0 tokens per session scan A 336168ea239f
account 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 3,429 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.