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/educlopez/ccvitals/configuregit clone --depth 1 https://github.com/educlopez/ccvitalsWhat 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.00008 | $0.03583 |
| Opus 5 | $0.00004 | $0.01792 |
| Sonnet 5 | $0.00002 | $0.00717 |
| Haiku 4.5 | $0.00001 | $0.00358 |
Grade A, and why
configure 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reconfigure ccvitals module selection and optional two-line layout.
Steps
1. Determine the Claude config directory
echo "${CLAUDE_CONFIG_DIR:-$HOME/.claude}"
Save the output as CONFIG_DIR.
2. Read the current config (if any)
cat "$CONFIG_DIR/.statusline-config.json" 2>/dev/null || echo "{}"
Show the user their current module list so they know what's active.
3. Ask which modules to enable
Use AskUserQuestion to ask:
Which modules do you want to enable? Current: [show current modules]
Core modules (default on):
- directory — current project folder name
- model — active model name
- context — context window bar + percentage
- usage — 5h quota bar, reset timer, plan badge
- git — branch name, changed files, lines diff
Optional modules (opt-in):
- rtk — RTK token-savings % (needs
rtkCLI)- codegraph — CodeGraph index size (needs
codegraphCLI)- lines — cumulative lines added/removed this session
- mode — reasoning effort level + fast-mode flag
- cost — session cost in USD (e.g. $0.42)
- duration — session wall-clock time (e.g. 1h23m)
- speed — token throughput in tok/s
- vim — vim mode indicator (N/I/V/VL)
- agent — active agent name
- pr — linked PR number and review state
- weekly — 7-day quota bar with reset countdown
- pace — burn-rate vs quota window (e.g.
pace +12%)- cache — prompt-cache freshness countdown (e.g.
cache 4m12s)- tools — tools currently in flight (e.g.
⚒ Bash +2); reads transcript (tail-bounded)- agents — active sub-agents (e.g.
◉ code-reviewer); reads transcript (tail-bounded)- todos — latest TodoWrite progress (e.g.
☑ 3/7); reads transcript (tail-bounded)- daily — cross-session daily spend (e.g.
Σ $4.20); optionaldaily_budgetfor coloring- compactions — compact_boundary count (e.g.
↯ 2); reads full transcript via grep- tokens — cumulative session input/output tokens (e.g.
⇅ 1.2M/45k); incremental cacheList all modules you want enabled, separated by spaces. Example:
directory model context usage git lines mode
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 · 347 lines · 8 tokens per session scan A 9565dc6cdfa4
configure is a command published in the GitHub repository educlopez/ccvitals (9 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 3,583 once invoked, about $0.0000 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
setup
Install the claude-pace statusline bundled with this plugin.
setup
Configure the statusline in Claude Code settings.
cleanup
Remove statusline configuration before uninstalling the plugin.
sync
Stage, commit, and push pending changes via the gss skill in one guided flow.
tmux-agent
Orchestrate parallel agents via tmux-mgr (start / list / complete / cleanup).
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.