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 juuni26/claude-notif-sound/plugin install notif-soundWrote 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/commands/juuni26/claude-notif-sound/verify)<a href="https://agentmods.dev/commands/juuni26/claude-notif-sound/verify"><img src="https://agentmods.dev/badge/commands/juuni26/claude-notif-sound/verify.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.00027 | $0.00364 |
| Opus 5 | $0.00014 | $0.00182 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00003 | $0.00036 |
Grade A, and why
verify 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 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.
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
Verify Setup
Check that the notif-sound plugin is correctly set up and ready to play sounds.
Run ALL of these checks:
- Fix permissions (make scripts executable):
chmod +x "${CLAUDE_PLUGIN_ROOT}/scripts/play-sound.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/gui-server.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/gui-server.py" 2>/dev/null && echo "Permissions OK"
- Check sound files exist:
ls -1 "${CLAUDE_PLUGIN_ROOT}/sounds/" 2>/dev/null | grep -E '\.(mp3|wav)$' || echo "NO_SOUNDS"
- Check data directory and config:
mkdir -p "${CLAUDE_PLUGIN_DATA}" && echo "Data dir OK: ${CLAUDE_PLUGIN_DATA}"
cat "${CLAUDE_PLUGIN_DATA}/config.json" 2>/dev/null || echo '{"volume": 4} (using default)'
- Test playback:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/play-sound.sh"
- Present a summary to the user:
- Scripts: permissions fixed or already executable
- Sounds: count of .mp3/.wav files found
- Volume: current setting
- Playback: whether test sound played
- If anything is wrong, suggest the fix (e.g.,
/notif-sound:addif no sounds,/notif-sound:volumeto adjust volume) - Mention that
/notif-sound:guialso shows live status in the dashboard
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 · 43 lines · 27 tokens per session scan A 8e1f09095032
verify is a command published in the GitHub repository juuni26/claude-notif-sound (2 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 364 once invoked, about $0.0001 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 commands, from other repositories
skill-refresh
You are running inside a headless Claude Code session in the neo4j-skills repository. Goal: scan Neo4j release notes and deprecation pages, then update any SKILL.md and references/ files that are stale, outdated, or missing new features. Open no PRs or commits — output only file edits. The workflow will handle git and…
brand-setup
Configure a new brand profile with colors, fonts, logo, visual style, platforms, and compliance rules.
screens
Structures product UX screen design — inventory, flow, states, and reusable briefs for external design tools — without generating pixels or UI code.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
qa
Smoke or browser-walk a running app. Report only. Do not implement. Do not merge.
clean-check
Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.