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/sergei-aronsen/claude-code-toolkit/council-statsgit clone --depth 1 https://github.com/sergei-aronsen/claude-code-toolkitWrote 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/sergei-aronsen/claude-code-toolkit/council-stats)<a href="https://agentmods.dev/commands/sergei-aronsen/claude-code-toolkit/council-stats"><img src="https://agentmods.dev/badge/commands/sergei-aronsen/claude-code-toolkit/council-stats.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.1 | $0.00018 | $0.00535 |
| Opus 5 | $0.00009 | $0.00267 |
| Sonnet 5 | $0.00004 | $0.00107 |
| Haiku 4.5 | $0.00002 | $0.00053 |
Grade A, and why
council-stats 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.
What it actually says
/council-stats
Render Council token usage and cost from the local log
(~/.claude/council/usage.jsonl). No API calls — works offline.
Purpose
Show how many Council calls have been made, broken down by provider, model, and mode, with token counts and dollar cost. Use it to spot runaway spend, verify CLI mode is actually saving money, or pull a CSV for billing reconciliation.
When to Use
| Situation | Use /council-stats |
|---|---|
| Wonder where today's tokens went | --day |
| Monthly cost report | --month --csv |
| Audit a specific date range | --since 2026-04-01 --until 2026-04-30 |
| Validate that CLI mode is free | --total (CLI rows show $0.0000) |
Usage
When the user types /council-stats (or any of the period variants below),
run the corresponding brain stats invocation and present the output verbatim.
| User asks for | Command |
|---|---|
| Today / last 24h | brain stats --day |
| This week | brain stats --week |
| This month | brain stats --month |
| All time (default) | brain stats --total |
| Range | brain stats --since 2026-04-01 --until 2026-04-30 |
| Machine-readable | append --csv to any of the above |
The output is grouped by (provider, model, mode) and totals tokens + cost
in USD. Cost comes from ~/.claude/council/pricing.json overlaid on the
built-in DEFAULT_PRICING table. CLI calls (Gemini CLI, Codex CLI) are
priced at $0 per token because subscription covers them; their token counts
are estimated (chars / 4) and marked with estimated: true per record.
Notes
- The log is append-only and never sent off-machine. Delete it with
rm ~/.claude/council/usage.jsonlif you want to reset history. - Update
~/.claude/council/pricing.jsonwhen provider rates change. Local edits are preserved on toolkit update via the.upstream-new.jsonsidecar pattern.
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.
- 6d ago First seen · 53 lines · 18 tokens per session scan A 53612487bbf7
council-stats is a command published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 20d ago), licensed MIT. It adds 18 tokens to every session and 535 once invoked, about $0.0001 per session on Opus 5. 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.