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/set-speed)<a href="https://agentmods.dev/commands/paulpreibisch/agentvibes/set-speed"><img src="https://agentmods.dev/badge/commands/paulpreibisch/agentvibes/set-speed.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.00008 | $0.00338 |
| Opus 5 | $0.00004 | $0.00169 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
set-speed 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
Set Speech Speed
Control the speech rate for Piper TTS voices (Piper TTS doesn't support speed control).
Usage
/agent-vibes:set-speed 2x # Set main voice to 2x slower
/agent-vibes:set-speed target 2x # Set target language to 2x slower
/agent-vibes:set-speed 0.5x # Set main voice to 2x faster
/agent-vibes:set-speed target 3x # Set target language to 3x slower
/agent-vibes:set-speed normal # Reset to normal speed (1.0)
/agent-vibes:set-speed target normal # Reset target to normal speed
Speed Values
0.5xor-2x= 2x faster (half duration)1xornormal= Normal speed2xor+2x= 2x slower (double duration, great for learning)3xor+3x= 3x slower (triple duration, very slow)
Examples
# Make Spanish 2x slower for learning
/agent-vibes:set-speed target 2x
# Make main voice faster
/agent-vibes:set-speed 0.5x
# Reset target language to normal speed
/agent-vibes:set-speed target normal
!bash .claude/hooks/speed-manager.sh $ARGUMENTS
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 · 42 lines · 0 tokens per session scan A 9513f877200d
set-speed is a command published in the GitHub repository paulpreibisch/AgentVibes (153 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 8 tokens to every session and 338 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
video-subtitle
A video workflow for creating, translating, and permanently adding subtitles to video files. It can extract audio, turn speech into text, translate subtitle files, and burn subtitles into the video.
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.