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 Bangs00/claude-media-control/plugin install mediaWrote 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/bangs00/claude-media-control/statusline)<a href="https://agentmods.dev/skills/bangs00/claude-media-control/statusline"><img src="https://agentmods.dev/badge/skills/bangs00/claude-media-control/statusline.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.00152 | $0.06199 |
| Opus 5 | $0.00076 | $0.03099 |
| Sonnet 5 | $0.00030 | $0.01240 |
| Haiku 4.5 | $0.00015 | $0.00620 |
Grade B, and why
statusline 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
the segment. Enabling also wires the segment into `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Requested arrangement or style (may be empty): $ARGUMENTS
Current items, in render order (/ starts a new line):
!"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" config statusline.fields
Current settings — the style table below marks customized values *custom
(see also display.statusline, statusline.multiline, statusline.color):
!"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" config
How arrangement works
statusline.fields is an ordered list — the segment renders the items in
exactly the order they are saved. A / in the list starts a new line
(explicit layout: each line shows exactly the items placed on it; app
directly after track folds into it as (App); a line with nothing to show
disappears). Without /, items group automatically (app onto track,
adjacent progressbar+time, output/volume onto a neighbor) and
statusline.multiline on puts each group on its own line.
Numeric patterns — wherever an arrangement can be given ($ARGUMENTS, a
typed reply, an "Other" answer): digits name the items, / starts a new
line, digit order = display order, and digits left out are omitted:
| digit | item | looks like |
|---|---|---|
| 1 | track |
▶︎ Karma Police — Radiohead |
| 2 | app |
(Spotify) |
| 3 | volume |
🔉 ▄ 45% (🔇 when muted) |
| 4 | progressbar |
━━━━━━──── |
| 5 | time |
2:13/4:24 |
| 6 | output |
🎧 AirPods Pro (icon by device: 🔊 speakers · 🎧 Bluetooth/headphones · 📺 HDMI/DisplayPort · 📶 AirPlay) |
123/456 → track,app,volume,/,progressbar,time,output (two lines);
45/126 → progressbar,time,/,track,app,output; 15 → track,time.
Presets: Standard = 123456 one line, Stacked = 123/456 two lines
(a "compact" wish maps to 15 by intent).
The style model
Every visible part has a style.* config key:
| key | part | default |
|---|---|---|
style.track.title |
track title | bold |
style.track.artist |
artist name | italic |
style.app |
app name (Spotify) |
dim |
style.volume.icon |
volume icon glyph | auto (🔈/🔉/🔊 by level) |
style.volume.style |
volume bar shape | block (▄ height bar) |
style.volume.bar |
volume bar on/off | on (draws in the accent) |
style.volume.percent |
volume percent 45% |
dim |
style.progressbar.playing |
bar fill + ▶︎ accent while playing | green |
style.progressbar.paused |
bar fill + ⏸ accent while paused | yellow |
style.progressbar.style |
progress bar characters | line |
style.progressbar.length |
progress bar width in cells (1–60) | 20 |
style.progressbar.sprite |
sprite style: frames, cycling one per second |
● ○ |
style.progressbar.trail |
sprite style: the walked track |
━ |
style.progressbar.track |
sprite style: the track still ahead |
─ |
style.time.elapsed |
elapsed time 2:13 |
bold |
style.time.total |
total-time tail /4:24 |
dim |
style.output.icon |
output device icon | auto (by device kind) |
style.output |
output device name | dim |
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 · 346 lines · 152 tokens per session scan B 3db1eb53bccb
statusline is a skill published in the GitHub repository Bangs00/claude-media-control (4 stars, last pushed 1mo ago), licensed MIT. It adds 152 tokens to every session and 6,199 once invoked, about $0.0008 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
apple-mail
Interact with Apple Mail on macOS. Use for reading, sending, searching, and managing emails.
high-output-management
Manage for output using Grove's "High Output Management": a manager's output is their organization's output, raised by high-leverage activities. Use when the user mentions "high output management", "managerial leverage", "one-on-ones", "1:1 agenda", "OKRs", "performance review", "task-relevant maturity", "delegation"…
37signals-way
Build lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat…
drive-motivation
Design motivation systems using Autonomy, Mastery, and Purpose (AMP) for products and teams. Use when the user mentions "intrinsic motivation", "gamification isnt working", "rewards arent working", "autonomy", "mastery", "purpose-driven", "my team is disengaged", or "how do I motivate people". Also trigger when…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
collaboration-platform-administration
Administers the email, chat, meeting and file-sharing platform the organization runs on — tenant and domain configuration, mail authentication and routing, phishing and spam controls, shared mailboxes and distribution groups, external sharing and guest access, permission sprawl in file storage, and retention and legal…