Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add SYM1000/claude-statusbar/plugin install statusbarWrote 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/skills/sym1000/claude-statusbar/config)<a href="https://agentmods.dev/skills/sym1000/claude-statusbar/config"><img src="https://agentmods.dev/badge/skills/sym1000/claude-statusbar/config.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.00080 | $0.03469 |
| Opus 5 | $0.00040 | $0.01734 |
| Sonnet 5 | $0.00016 | $0.00694 |
| Haiku 4.5 | $0.00008 | $0.00347 |
Grade A, and why
config 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 8d 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 — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statusbar — Interactive Configuration
You are helping the user configure their statusbar plugin. You will present a visual, interactive configuration experience using Claude Code's native selection UI, then save their choices.
Check for preset argument
If the user provided a preset name as an argument (e.g., /statusbar:config developer), skip the interactive UI and jump directly to Apply Preset below.
Available presets and their widget mappings:
| Preset | Layout | Enabled widgets |
|---|---|---|
minimal |
compact | compact-warn, model, effort, context |
default |
compact | compact-warn, model, effort, context, cost, duration, git |
developer |
standard | compact-warn, model, effort, context, cost, duration, git, lines, rate-5h, rate-7d, tokens, cache, latency, context-size |
full |
mascot | ALL widgets enabled |
tracker |
standard | compact-warn, model, effort, context, cost, duration, messages, total-tokens, tools-used |
Step 1: Read current configuration
Read the current config file to know the user's existing setup:
- Try
${CLAUDE_PLUGIN_DATA}/statusbar-config.json - Then try
${CLAUDE_PLUGIN_ROOT}/defaults/statusbar-config.json - Fall back to: layout=compact, widgets=compact-warn+model+context+cost+duration+git
Note the current layout and which widgets are enabled/disabled. You MUST use this to mark current state in the UI (see Step 2).
Step 2: Present the interactive configuration UI
Use a SINGLE AskUserQuestion call with exactly 4 questions (shown as navigable tabs). The user browses tabs with arrow keys, selects options with enter/space.
IMPORTANT: Show current state in options
The AskUserQuestion tool does not support pre-selecting options. To show the user what's currently enabled, you MUST dynamically modify the options based on the config you read in Step 1:
For multi-select questions (Q2, Q3, Q4):
- Append
[ON]to the label of each option whose widgets are currently enabled in the config - Append
[OFF]to the label of each option whose widgets are currently disabled - Add a note in the question text: "Options marked [ON] are currently enabled."
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.
- 8d ago First seen · 314 lines · 80 tokens per session scan A 36dfbae89cff
config is a skill published in the GitHub repository SYM1000/claude-statusbar (10 stars, last pushed 5mo ago), licensed MIT. It adds 80 tokens to every session and 3,469 once invoked, about $0.0004 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 skills, from other repositories
sw-handoff
Write a portable, secret-scrubbed handoff doc plus a diff of your uncommitted edits so another tool or machine resumes where you stopped. Use for "handoff", "out of tokens", "switch to Codex".
tokf-discover
Find missed token savings by scanning AI coding session files for commands that ran without tokf filtering.
handoff
Write a portable, secret-scrubbed handoff doc so this work can continue in any AI tool or on any machine. Use when saying "handoff", "running out of tokens", or "continue elsewhere".
docs
Use when documentation generally needs to catch up with a branch before pushing or merging, covering internal developer docs, external customer-facing docs, and release notes together — "update the docs", "do a docs pass before I merge", "make sure everything's documented". Prefer this when no single documentation…
claude-code-expert
Especialista profundo em Claude Code - CLI da Anthropic. Maximiza produtividade com atalhos, hooks, MCPs, configuracoes avancadas, workflows, CLAUDE.md, memoria, sub-agentes, permissoes e integracao com ecossistemas.
amq-spec
Use two agents to research a design independently and converge on one specification through AMQ. Trigger for collaborative design or messages labeled workflow:spec; use amq-cli for ordinary coordination.