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/bangs00/claude-media-control/volumenpx skills add Bangs00/claude-media-control --skill volumegit clone --depth 1 https://github.com/Bangs00/claude-media-controlWrote 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/volume)<a href="https://agentmods.dev/skills/bangs00/claude-media-control/volume"><img src="https://agentmods.dev/badge/skills/bangs00/claude-media-control/volume.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.00043 | $0.00351 |
| Opus 5 | $0.00022 | $0.00176 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
volume 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 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.
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.
What it actually says
Requested volume: $ARGUMENTS
- Work out the target:
- no argument → just read the current volume
- a number 0-100 → set that level
- relative ("louder", "quieter", "볼륨 올려/내려", "a bit louder") → read the current level first, then add/subtract 10 (clamp to [0, 100])
- "mute" → set 0; "unmute" without a remembered level → suggest 50
- Run with Bash:
"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" volume # read
"${CLAUDE_PLUGIN_ROOT}/scripts/media.sh" volume <0-100> # set, then reads back
The command prints {"volume":N,"muted":bool}. Confirm in one short markdown
line, e.g. 🔊 Volume **45%** (append *(muted)* when muted is true). This
is the system output volume — it does not change per-app sliders.
Tip: the statusline can show the volume as icon + level bar + percent
(🔉 ▄ 45%) — check "Volume" in the /media:statusline Items tab, or place
it anywhere with a numeric pattern (digit 3).
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 · 30 lines · 43 tokens per session scan A 6b0aca492c35
volume is a skill published in the GitHub repository Bangs00/claude-media-control (4 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 351 once invoked, about $0.0002 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
quiz-me
Quiz the user on root cause and intended fix BEFORE writing any non-trivial code, then verify comprehension of every change after. Use when the user asks for a bug fix, refactor, or feature and wants to stay technically sharp instead of vibe-coding. Also use when the user says "quiz me", "don't let me vibe code", or…
economist-style
Apply The Economist style guide to written content. Use when editing markdown, HTML, documentation, or any written text that needs professional editing for clarity, precision, and brevity. Detects weasel words, fillers, passive voice, and style issues.
configure
Set up the telegram-topics channel — save the bot token and forum group id, then run a preflight check. Use when the user pastes a Telegram bot token, asks to configure telegram-topics, asks "how do I set this up", or wants to check channel status.
access
Manage who may drive telegram-topics sessions — view and edit the user allowlist. Use when the user asks to allow or remove a Telegram user, check who's allowed, or lock the channel down.
allowlist
Put this plugin on the Claude Code channels allowlist (managed settings) so --channels delivers inbound messages — one command, one admin prompt. Use when preflight reports NOT ALLOWLISTED, when Telegram messages never arrive in sessions although the send tools work, or when the user asks to set up the channels…
spotify
Control Spotify on macOS. Use for playing music, controlling playback, and getting track information.