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 skills/sym1000/claude-statusbar/setupnpx skills add SYM1000/claude-statusbar --skill setupgit clone --depth 1 https://github.com/SYM1000/claude-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/setup)<a href="https://agentmods.dev/skills/sym1000/claude-statusbar/setup"><img src="https://agentmods.dev/badge/skills/sym1000/claude-statusbar/setup.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.00074 | $0.00653 |
| Opus 5 | $0.00037 | $0.00327 |
| Sonnet 5 | $0.00015 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00065 |
Grade B, and why
setup 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 3d 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.
- The setup helper writes to `~/.claude/settings.json` — it preserves all existing settings and only adds/modifies the `statusLine` key How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Statusbar — Setup
You are helping the user set up, check, or uninstall the statusbar plugin.
Determine the action
Based on the user's message, determine which action to perform:
- setup (default): Configure the status bar for first-time use
- uninstall: Remove the status bar configuration
- status: Check current configuration state
If the user just typed /statusbar:setup with no additional context, assume setup.
Step 1: Check current status
Run the setup helper to check the current state:
node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-helper.js" status --plugin-root "${CLAUDE_PLUGIN_ROOT}" --data-dir "${CLAUDE_PLUGIN_DATA}"
Parse the JSON output. Report to the user:
- Whether the status bar is currently configured
- Which data directory is being used
- Current layout and enabled widgets (if configured)
Step 2: Execute the action
For setup:
If the status bar is already configured, tell the user it's already set up and ask if they want to re-run setup (which will overwrite their statusLine setting).
If proceeding with setup, run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-helper.js" setup --plugin-root "${CLAUDE_PLUGIN_ROOT}" --data-dir "${CLAUDE_PLUGIN_DATA}"
Parse the JSON output. If successful, tell the user:
- Status bar is now configured!
- They need to restart Claude Code for the status bar to appear
- After restarting, they can customize the status bar with
/statusbar:config - Show the default widgets that are enabled: model, context usage, cost, duration, git branch
If any step failed, show the error and suggest manual troubleshooting.
For uninstall:
Confirm with the user before proceeding. Then run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/setup-helper.js" uninstall --plugin-root "${CLAUDE_PLUGIN_ROOT}" --data-dir "${CLAUDE_PLUGIN_DATA}"
Tell the user the status bar has been removed and they need to restart Claude Code.
For status:
Just display the status information from Step 1 in a readable format. If not configured, suggest running /statusbar:setup.
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.
- 3d ago First seen · 77 lines · 74 tokens per session scan B a0277ddbbcb9
setup is a skill published in the GitHub repository SYM1000/claude-statusbar (10 stars, last pushed 5mo ago), licensed MIT. It adds 74 tokens to every session and 653 once invoked, about $0.0004 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-31.
Other skills, from other repositories
youtube-to-markdown
Use when user asks YouTube video extraction, get, fetch, transcripts, subtitles, or captions. Writes video details and transcription into structured markdown file.
youtube-to-markdown
Use when user asks YouTube video extraction, get, fetch, transcripts, subtitles, or captions. Writes video details and transcription into structured markdown file.
youtube-to-markdown
Use when user asks YouTube video extraction, get, fetch, transcripts, subtitles, or captions. Writes video details and transcription into structured markdown file.
youtube-to-markdown
Use when user asks YouTube video extraction, get, fetch, transcripts, subtitles, or captions. Writes video details and transcription into structured markdown file.
youtube-to-markdown
Use when user asks YouTube video extraction, get, fetch, transcripts, subtitles, or captions, or channel browsing. Writes video details and transcription into structured markdown file.
chrome-control
Use when debugging web applications, diagnosing page errors, inspecting console output, or capturing screenshots via Chrome DevTools Protocol (CDP).