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/background-music)<a href="https://agentmods.dev/commands/paulpreibisch/agentvibes/background-music"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/background-music.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.00011 | $0.01055 |
| Opus 5 | $0.00005 | $0.00528 |
| Sonnet 5 | $0.00002 | $0.00211 |
| Haiku 4.5 | $0.00001 | $0.00105 |
Grade A, and why
background-music 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: When user requests background music changes in natural language (e.g., "change to salsa", "switch to jazz"), you MUST:
- Run
.claude/hooks/background-music-manager.sh listto see all available tracks - Find the matching track by searching for keywords (e.g., "salsa" → "agent_vibes_salsa_v2_loop.mp3")
- Execute
.claude/hooks/background-music-manager.sh set-default EXACT_FILENAME - Test with TTS to confirm the change took effect
CRITICAL PATH INFORMATION:
- The script is ALWAYS at
.claude/hooks/background-music-manager.sh(relative to current directory) - DO NOT use global paths like
/agent-vibes/cli.shor~/.agentvibes/cli.sh - DO NOT search for the script - it's always in the same location
- Use either
bash .claude/hooks/background-music-manager.shOR just.claude/hooks/background-music-manager.sh
NEVER:
- Search for background-music-manager.sh (you already know where it is)
- Use global installation paths
- Manually edit config files directly
- Create new config files like "background-music.cfg"
- Guess filenames without listing them first
Run the background music manager script with the provided command.
If no arguments provided, show status. Otherwise execute:
bash .claude/hooks/background-music-manager.sh {command}
Valid commands: on, off, status, list, volume {0.0-1.0}, set-default {filename}, set-agent {agent_name} {filename}, set-all {filename}
Control background music that plays behind TTS voice output.
Usage
/agent-vibes:background-music- Show current status/agent-vibes:background-music on- Enable background music/agent-vibes:background-music off- Disable background music/agent-vibes:background-music volume 0.3- Set volume (0.0-1.0)/agent-vibes:background-music list- List all pre-packaged background music tracks/agent-vibes:background-music set-default TRACK- Set default background music track/agent-vibes:background-music set-agent AGENT TRACK- Set background music for a specific agent/agent-vibes:background-music set-all TRACK- Set the same background music for all agents
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.
- 8d ago First seen · 112 lines · 11 tokens per session scan A 21495a8fd1de
background-music is a command published in the GitHub repository paulpreibisch/AgentVibes (153 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,055 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-30.
Other commands, from other repositories
innovator
Creative problem solving with WebSearch and Memory integration.
audit-code
When /audit-code [target] is invoked, immediately execute the following steps to analyze code quality, security, and adherence to project standards.
transcribe
Transcribe the file at $ARGUMENTS into Markdown using the Frenchie MCP server.
imperium:create-video
Create startup video content. Supports pitch videos, product demos, social clips, investor updates, and hiring videos. Bridges to Remotion for rendering.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.