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.
git clone --depth 1 https://github.com/vibe-with-me-tools/agent-reachoutWrote 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/vibe-with-me-tools/agent-reachout/agent-reachout)<a href="https://agentmods.dev/plugins/vibe-with-me-tools/agent-reachout/agent-reachout"><img src="https://agentmods.dev/badge/plugins/vibe-with-me-tools/agent-reachout/agent-reachout/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/plugins/vibe-with-me-tools/agent-reachout/agent-reachout"><img src="https://agentmods.dev/badge/plugins/vibe-with-me-tools/agent-reachout/agent-reachout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
agent-reachout 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 9d 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": "agent-reachout",
"version": "1.0.3",
"description": "Multi-provider notification plugin for Claude Code",
"author": {
"name": "vibe-with-me-tools",
"url": "https://github.com/vibe-with-me-tools"
},
"repository": "https://github.com/vibe-with-me-tools/agent-reachout",
"license": "MIT",
"keywords": [
"notifications",
"telegram",
"messaging",
"alerts",
"claude-code-plugin",
"llm-notifications"
],
"mcpServers": {
"agent-reachout": {
"command": "bun",
"args": [
"run",
"--cwd",
"${CLAUDE_PLUGIN_ROOT}/server",
"start"
],
"env": {
"AGENT_REACHOUT_TELEGRAM_BOT_TOKEN": "${AGENT_REACHOUT_TELEGRAM_BOT_TOKEN}",
"AGENT_REACHOUT_TELEGRAM_CHAT_ID": "${AGENT_REACHOUT_TELEGRAM_CHAT_ID}"
}
}
}
}What it installs
The manifest is a name and a version. 2 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 ships with it
1 file beside plugin.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.
- 9d ago First seen · 34 lines scan A d381e9050097
agent-reachout is a plugin published in the GitHub repository vibe-with-me-tools/agent-reachout (54 stars, last pushed 5mo 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-30.
Other plugins, from other repositories
token-saver
Automatically compresses verbose CLI output (git, docker, npm, terraform, kubectl, etc.) to save tokens in Claude Code sessions. 36 specialized processors with content-aware compression.
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.
cc-sounds marketplace
Notification sounds for Claude Code on Windows: distinct cues for task-complete, needs-input, and error, played only when the terminal is backgrounded.
cc-sounds
Windows notification sounds for Claude Code: finish, error and input-needed alerts. Plays only when the terminal is in the background so it never interrupts active work.
notifications
Sound + desktop notifications when Claude Code needs your attention or finishes a task (Linux & macOS).
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.