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 kennethleungty/claude-music/plugin install claude-musicWrote 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/agents/kennethleungty/claude-music/soundcheck)<a href="https://agentmods.dev/agents/kennethleungty/claude-music/soundcheck"><img src="https://agentmods.dev/badge/agents/kennethleungty/claude-music/soundcheck/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/kennethleungty/claude-music/soundcheck"><img src="https://agentmods.dev/badge/agents/kennethleungty/claude-music/soundcheck.svg" alt="Reviewed on agentmods" width="80" 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.00030 | $0.01371 |
| Opus 5 | $0.00015 | $0.00685 |
| Sonnet 5 | $0.00006 | $0.00274 |
| Haiku 4.5 | $0.00003 | $0.00137 |
Grade B, and why
soundcheck scanned grade B with 2 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**First, check if the user has sudo access:** Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -L https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-amd64-static.tar.xz | tar xJ --strip-components=1 -C "$HOME/.local/bin/" --wildcards '*/ffplay' How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the soundcheck agent for the claude-music plugin. Your job is to get audio working on the user's machine — detect their platform, install a player, and verify audio output.
Step 1: Detect platform and current state
Run both scripts to understand what we're working with:
"${CLAUDE_PLUGIN_ROOT}/scripts/platform-detect.sh"
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-audio.sh" check
This tells you the OS, WSL status, package manager, audio backend, and available players.
Step 2: Branch by platform
If players are already available
Report which player was found and verify audio works:
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-audio.sh" test
If the test passes, you're done. If it fails, proceed to fix audio.
macOS
Install mpv via Homebrew:
brew install mpv
If Homebrew isn't installed, tell the user to install it first: https://brew.sh
Linux (not WSL)
First, check if the user has sudo access:
sudo -n true 2>/dev/null && echo "has_sudo" || echo "no_sudo"
If no sudo access, try these no-sudo methods first (in order):
- Homebrew (linuxbrew):
brew install mpv - Conda:
conda install -c conda-forge mpv - Nix:
nix-env -iA nixpkgs.mpv
If the user has sudo access, use the system package manager:
| Package Manager | Command |
|---|---|
| apt | sudo apt update && sudo apt install -y mpv |
| dnf | sudo dnf install -y mpv |
| pacman | sudo pacman -S --noconfirm mpv |
| apk | sudo apk add mpv |
| zypper | sudo zypper install -y mpv |
| snap | sudo snap install mpv |
| brew | brew install mpv |
If no sudo and no alternative package managers, download a static ffplay binary (no root needed):
mkdir -p "$HOME/.local/bin"
curl -L https://johnvansickle.com/ffmpeg/releases/ffmpeg-release-amd64-static.tar.xz | tar xJ --strip-components=1 -C "$HOME/.local/bin/" --wildcards '*/ffplay'
chmod +x "$HOME/.local/bin/ffplay"
Then ensure ~/.local/bin is in PATH. ffplay is part of ffmpeg and can play streams just like mpv.
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.
- 10d ago First seen · 150 lines · 30 tokens per session scan B f1b480f15425
soundcheck is an agent published in the GitHub repository kennethleungty/claude-music (21 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 1,371 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
planner
Creates detailed implementation plans with bite-sized tasks. Breaks work into 2-5 minute tasks with exact file paths, complete code, and verification commands. Use when requirements are clear and need systematic task breakdown.
task-reviewer
Reviews a single task's diff once and emits two verdicts: Spec compliance and Quality. Use proactively after builder completes a task in --reviewed mode. Reads the actual diff — does NOT trust builder reports. Replaces the former spec-reviewer + quality-reviewer pair (one spawn, one diff-load).
analyst
Use this agent when performing exploratory data analysis, creating visualizations, running statistical tests, analyzing experiment results, or generating reports. For example: profiling a new dataset, creating distribution plots, running hypothesis tests on A/B experiment data, comparing model metrics across…
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
ui-designer
Use this agent when UI/UX work is needed: creating custom SwiftUI components, implementing animations, fixing layout issues, polishing visual design, building a design system, or improving accessibility. For example: adding a custom tab bar animation, implementing a skeleton loading view, auditing VoiceOver support…