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.
/plugin marketplace add Fergal7/cc-soundsnpx agentmods add plugins/fergal7/cc-sounds/marketplacegit clone --depth 1 https://github.com/Fergal7/cc-soundsWrote 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/plugins/fergal7/cc-sounds/marketplace)<a href="https://agentmods.dev/plugins/fergal7/cc-sounds/marketplace"><img src="https://agentmods.dev/badge/plugins/fergal7/cc-sounds/marketplace.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cc-sounds marketplace 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 3d 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
{
"name": "cc-sounds",
"description": "Notification sounds for Claude Code on Windows: distinct cues for task-complete, needs-input, and error, played only when the terminal is backgrounded.",
"owner": {
"name": "Fergal7"
},
"plugins": [
{
"name": "cc-sounds",
"description": "Windows notification sounds for Claude Code (finish / error / input-needed).",
"source": {
"source": "github",
"repo": "Fergal7/cc-sounds",
"ref": "v1.1.1",
"sha": "28b45ade814964fcab656baf38a09a5d6225a5b7"
}
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 3d ago First seen · 20 lines scan A 3797bcba40c9
cc-sounds marketplace is a plugin published in the GitHub repository Fergal7/cc-sounds (1 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
ntfy-mcp-server
Send, manage, and replay ntfy push notifications via MCP. STDIO or Streamable HTTP.
navi
Floating macOS window that monitors Claude Code sessions with Working/Idle status, inline permission approve/deny, session discovery, per-event sounds, and menu bar icon.
agent-reachout
Multi-provider notification plugin for Claude Code.
notifications
Sound + desktop notifications when Claude Code needs your attention or finishes a task (Linux & macOS).
notify
Cross-platform system notifications for Claude Code — macOS and Linux with a notification cooldown.
claude-callout
Voice + OS notifications when Claude is waiting on you or finished a turn. Cross-platform, focus-aware, with quiet hours and 10s debounce to keep noise low.