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 TakashiKakizoe1109/cc-notifier-voicenpx agentmods add plugins/takashikakizoe1109/cc-notifier-voice/plugingit clone --depth 1 https://github.com/TakashiKakizoe1109/cc-notifier-voiceWrote 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/takashikakizoe1109/cc-notifier-voice/plugin)<a href="https://agentmods.dev/plugins/takashikakizoe1109/cc-notifier-voice/plugin"><img src="https://agentmods.dev/badge/plugins/takashikakizoe1109/cc-notifier-voice/plugin.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
cc-notifier-voice 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-notifier-voice",
"version": "0.2.1",
"description": "Desktop notifications with voice announcements and Slack integration for Claude Code events (macOS/Windows/WSL2)",
"author": {
"name": "Takashi Kakizoe"
},
"repository": "https://github.com/TakashiKakizoe1109/cc-notifier-voice",
"homepage": "https://github.com/TakashiKakizoe1109/cc-notifier-voice",
"license": "MIT",
"keywords": [
"notification",
"voice",
"tts",
"macos",
"windows",
"wsl2",
"slack"
]
}
What it installs
The manifest is a name and a version. 7 hooks travel with it, and installing the plugin installs all of them. Each is measured on its own page, and each can be installed alone.
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 · 21 lines scan A aba3ea95d25f
cc-notifier-voice is a plugin published in the GitHub repository TakashiKakizoe1109/cc-notifier-voice (1 stars, last pushed 6mo 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
iterm2-tab-status
Show iTerm2 tab status (running/idle/attention) for Claude Code sessions.
audio-recap
Audio Recap for Claude Code — listen to each assistant turn: a one-sentence recap of what Claude did, then the message itself, with long replies summarized for ears.
touch-grass
Local cat-GIF break reminder banners for long vibe-coding sessions.
claude-speak
Give Claude a voice on macOS (say) or Linux (espeak-ng) — on-demand /speak (verbatim or LLM-summarized), an automatic toggle-speak Stop hook, and adjustable rate/voice/truncation.
relay
Delegate work packets from a lead Claude Code session to executor sessions in their own iTerm tabs, with session reuse instead of always spawning fresh.
vscode-tab
Rename the active Claude Code session tab in VS Code. Handles Japanese, ASCII, and mixed-script names by bypassing the IME.