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.
npx skills add paulpreibisch/AgentVibes --skill agentvibes-grokbot-tts-setupgit 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/skills/paulpreibisch/agentvibes/agentvibes-grokbot-tts-setup)<a href="https://agentmods.dev/skills/paulpreibisch/agentvibes/agentvibes-grokbot-tts-setup"><img src="https://agentmods.dev/badge/skills/paulpreibisch/agentvibes/agentvibes-grokbot-tts-setup/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/skills/paulpreibisch/agentvibes/agentvibes-grokbot-tts-setup"><img src="https://agentmods.dev/badge/skills/paulpreibisch/agentvibes/agentvibes-grokbot-tts-setup.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.00047 | $0.00705 |
| Opus 5.5 | $0.00019 | $0.00282 |
| Sonnet 5.5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
AgentVibes GrokBot TTS setup 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 29d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Install AgentVibes + Kokoro for a GrokBot fleet
Goal
Install AgentVibes and Kokoro on the user's Windows machine, set Kokoro as the TTS provider, and give each GrokBot a unique -llm identity, Kokoro voice, and spoken name so speech plays on local speakers.
Prerequisites
- Windows machine available via Shell (Node.js + Python 3)
- Permission to install npm/pip packages on that machine
Steps
1. Install AgentVibes
npx agentvibes install
Open the TUI anytime with:
npx agentvibes
2. Install Kokoro
pip install kokoro soundfile numpy
If pip is missing:
python -m pip install kokoro soundfile numpy
3. Set provider to Kokoro
Prefer the AgentVibes TUI provider picker. On Windows you can also run:
powershell -NoProfile -ExecutionPolicy Bypass -File "$env:USERPROFILE\.claude\hooks-windows\provider-manager.ps1" set kokoro
(If AgentVibes installed under a project .claude folder, use that hooks-windows path instead.)
4. Verify speech
Play a short test line via play-tts.ps1 (under AgentVibes .claude\hooks-windows) and confirm audio on the local speakers.
5. Assign fleet voices
For each GrokBot, add one row to audio-effects.cfg:
llm:<key>|light||0.20|<kokoro_voice>|<Spoken Name> GrokBot|kokoro
Rules:
- One unique Kokoro voice per bot (no reuse)
- Spoken pretext must identify the bot (e.g.
Chief of Staff GrokBot) - Mirror rows into both project and user
.claude\config\audio-effects.cfgwhen both exist - Update
%USERPROFILE%\.grokbot\agentvibes-tts.mdif that cheat sheet exists
Example voices: am_michael, am_adam, bm_george, af_bella, af_nicole, af_sarah, bm_lewis.
6. Teach each bot to speak
Each bot should call:
& "<AgentVibes>\.claude\hooks-windows\play-tts.ps1" -Text "Short update." -llm "<their-key>"
Keep spoken lines short; the pretext carries identity.
7. Prove it
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.
- 29d ago First seen · 95 lines · 47 tokens per session scan A f59c3542ac32
AgentVibes GrokBot TTS setup is a skill published in the GitHub repository paulpreibisch/AgentVibes (156 stars, last pushed 2d ago), licensed Apache-2.0. It adds 47 tokens to every session and 705 once invoked, about $0.0002 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-17.
Other skills, from other repositories
prismer-python-debugpy
Debug Python: pdb REPL + debugpy remote (DAP).
python-linting
Lint and format Python code using ruff, flake8, black, and mypy according to standard conventions. Use when asked to lint, format, or check style/type issues in Python files.
sqlalchemy-models
Create or modify SQLAlchemy models, queries, and Alembic migrations. Use when: defining new database tables, writing queries, creating migrations, checking model conventions, or understanding the database layer.
fastapi-routes
Create or modify FastAPI routes. Use when: adding new API endpoints, creating Pydantic request/response models, registering routers, designing REST APIs, or following route conventions for this project.
python-testing
Write or modify Python tests. Use when: adding new tests, understanding testing conventions, working with fixtures, writing FastAPI route tests, database tests, or following pytest patterns. DO NOT USE FOR RUNNING TESTS. If you are just running tests, not building them, you do not need this.
typer-cli
Add or modify CLI commands using Typer. Use when: adding new CLI subcommands, wrapping async functions for CLI use, understanding the CLI entrypoint structure, or following the @syncify pattern for async commands.