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/lacolaco/claude-plugins/volumenpx skills add lacolaco/claude-plugins --skill volumegit clone --depth 1 https://github.com/lacolaco/claude-pluginsWhat 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.00091 | $0.00357 |
| Opus 5 | $0.00046 | $0.00179 |
| Sonnet 5 | $0.00018 | $0.00071 |
| Haiku 4.5 | $0.00009 | $0.00036 |
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 2d 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
TTS volume ($ARGUMENTS)
The session-tts plugin pipes every chunk through afplay --volume <coefficient> so TTS does not dominate over other audio (notifications, music) when the system volume is up. macOS has no native way to make afplay follow the system "alert volume"; this skill is the override path.
The chosen value lives at $HOME/.claude/session-tts/volume and is read by say-response.py for every chunk it plays. The setting is per-user, not per-session — adjusting it affects every active and future session. A value outside [0.0, 1.0] is rejected; an empty file or missing file falls back to SESSION_TTS_VOLUME env var (if set), then to the built-in default (0.8). reset removes the volume file, reverting to the env var or built-in default.
Run the action below with the Bash tool. Default to status when $ARGUMENTS is empty.
bash "${CLAUDE_PLUGIN_ROOT}/skills/volume/volume.sh" "$ARGUMENTS"
Execute the requested action and report the resulting line. No additional explanation is needed.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 19 lines · 91 tokens per session scan A 5e96a23e3125
volume is a skill published in the GitHub repository lacolaco/claude-plugins (5 stars, last pushed 7d ago), licensed MIT. It adds 91 tokens to every session and 357 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…