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/paulpreibisch/AgentVibesWrote 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/paulpreibisch/agentvibes/receiver)<a href="https://agentmods.dev/commands/paulpreibisch/agentvibes/receiver"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/receiver/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/commands/paulpreibisch/agentvibes/receiver"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/receiver.svg" alt="Reviewed on agentmods" width="80" 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.00730 |
| Opus 5.5 | $0.00011 | $0.00292 |
| Sonnet 5.5 | $0.00005 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
receiver 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 1mo 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
AgentVibes Master Switch (Receiver + Local)
This machine can speak from two independent sources:
- Server-received TTS — arrives over SSH, is queued, and played by the
watcher through
play-tts.ps1, which checks~/.claude/tts-muted.txt. - Local text TTS — the local Claude Code hooks. The Windows hook
(
play-tts.ps1) checks~/.claude/tts-muted.txt; the bash hook (play-tts.sh) checks~/.agentvibes-muted.
A single mute file only covers part of this, so this command sets all
of them at once. off silences everything; on restores everything.
Run the block below. The user's requested mode is in $ARGUMENTS
(e.g. on, off, or empty/status to just report).
set -euo pipefail
ARG="$(printf '%s' "${ARGUMENTS:-}" | tr '[:upper:]' '[:lower:]' | tr -d '[:space:]')"
WIN_MUTE="$HOME/.claude/tts-muted.txt" # gates play-tts.ps1 (receiver + local Windows)
BASH_MUTE="$HOME/.agentvibes-muted" # gates play-tts.sh (local bash hook)
mkdir -p "$HOME/.claude"
report_state() {
local w="false" b="absent"
[ -f "$WIN_MUTE" ] && w="$(tr -d '[:space:]' < "$WIN_MUTE" 2>/dev/null || echo '?')"
[ -f "$BASH_MUTE" ] && b="present"
if [ "$w" = "true" ] || [ "$b" = "present" ]; then
echo "🔇 AgentVibes is OFF (muted) — windows=$w bash=$b"
else
echo "🔊 AgentVibes is ON (unmuted) — windows=$w bash=$b"
fi
}
case "$ARG" in
off|mute|silence|stop|quiet|0|false)
printf 'true' > "$WIN_MUTE"
: > "$BASH_MUTE"
# Drop any project-level override that could re-enable local TTS in the cwd.
rm -f "./.claude/agentvibes-unmuted" 2>/dev/null || true
echo "🔇 **AgentVibes OFF.** Both server-received and local TTS are now muted on this machine."
;;
on|unmute|sound|start|speak|1|true)
printf 'false' > "$WIN_MUTE"
rm -f "$BASH_MUTE"
rm -f "./.claude/agentvibes-muted" 2>/dev/null || true
echo "🔊 **AgentVibes ON.** Both server-received and local TTS are now active on this machine."
;;
""|status|check|state)
report_state
;;
*)
echo "Usage: /agent-vibes:receiver on | off | status"
report_state
;;
esac
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.
- 1mo ago First seen · 65 lines · 27 tokens per session scan A 6f141f05f5da
receiver is a command published in the GitHub repository paulpreibisch/AgentVibes (156 stars, last pushed 2d ago), licensed Apache-2.0. It adds 27 tokens to every session and 730 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
delivery-profiles
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
plan-delegate
Execution: work a roadmap as supervisor, brief an implementation agent per item, verify its work independently, then record and commit it.
sparc-post-deployment-monitoring-mode
📈 Deployment Monitor - You observe the system post-launch, collecting performance, logs, and user feedback. You flag reg...
setup
Command "setup" from jazz-max/ruflo-hub, covering setting up ruv-swarm hooks, quick start, 1. initialize with hooks, 2. test hook functionality and test pre-edit hook.