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/leeguooooo/claude-code-usage-bar/statusbar-doctorgit clone --depth 1 https://github.com/leeguooooo/claude-code-usage-barWrote 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/leeguooooo/claude-code-usage-bar/statusbar-doctor)<a href="https://agentmods.dev/commands/leeguooooo/claude-code-usage-bar/statusbar-doctor"><img src="https://agentmods.dev/badge/commands/leeguooooo/claude-code-usage-bar/statusbar-doctor.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.00014 | $0.00228 |
| Opus 5 | $0.00007 | $0.00114 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade B, and why
statusbar-doctor scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Whether `~/.claude/settings.json` has our statusLine entry (and whether something else is occupying it) What it actually says
Status Bar — doctor
Run:
cs doctor
The output covers:
- Whether
csis on PATH and where it resolves to - Version + Python interpreter
- Whether
~/.claude/settings.jsonhas our statusLine entry (and whether something else is occupying it) - Last
last_stdin.jsoncache age (i.e. is Claude Code actually pushing data) - Terminal size and
TERM - Current resolved
style/theme/show_*toggles - Number of
/statusbar*slash commands installed
Show the user the full output as-is. If anything is flagged with ✗, point at that line specifically and propose the obvious next step (cs --setup to create the statusLine entry, cs upgrade to upgrade — never a raw pip/uv command, cs upgrade picks the channel the install actually uses, etc.). Don't editorialize beyond what the output already says.
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.
- 5d ago First seen · 25 lines · 14 tokens per session scan B 528a33daf5a1
statusbar-doctor is a command published in the GitHub repository leeguooooo/claude-code-usage-bar (364 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 228 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
context-stats
Display context window usage and token statistics.
run
Execute prompt(s) from ./prompts/ with automatic archiving - for structured prompt-based work.
help
Explain Ralph Wiggum technique and available commands.
cancel-ralph
Cancel active Ralph Wiggum loop.
backup-config
Backup Claude Code configuration files.
session-log
View and analyze the Claude Code session log.