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/remove)<a href="https://agentmods.dev/commands/juuni26/claude-notif-sound/remove"><img src="https://agentmods.dev/badge/commands/juuni26/claude-notif-sound/remove.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.00022 | $0.00176 |
| Opus 5 | $0.00011 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
remove 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 6d 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
Remove Sound
The user wants to remove a sound file from the plugin.
- Check if the file exists in the sounds directory:
ls "${CLAUDE_PLUGIN_ROOT}/sounds/" | grep -E '\.(mp3|wav)$'
- If
$ARGUMENTSmatches a file, show the full path and confirm deletion - Delete the file (use basename to prevent path traversal):
SAFE_NAME="$(basename "$ARGUMENTS")"
rm "${CLAUDE_PLUGIN_ROOT}/sounds/$SAFE_NAME"
- Confirm removal to the user
- If not found, list available sounds so the user can pick the right name
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.
- 6d ago First seen · 26 lines · 22 tokens per session scan A 5e9aef7f9a16
remove is a command published in the GitHub repository juuni26/claude-notif-sound (2 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 176 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
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.
reset
Guided teardown of an organic-os site - what gets deregistered automatically, what you must delete or revoke yourself, and why.