Voicebox is a local AI voice studio that clones voices, generates speech, and turns spoken input into text on a computer. People use it for dictation, voice creation, and giving MCP-compatible agents spoken output. The catalogue add-ons support workflows around operating Voicebox.
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 agentmods add skills/jamiepine/voicebox/add-tts-enginenpx skills add jamiepine/voicebox --skill add-tts-enginegit clone --depth 1 https://github.com/jamiepine/voiceboxWrote 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/jamiepine/voicebox/add-tts-engine)<a href="https://agentmods.dev/skills/jamiepine/voicebox/add-tts-engine"><img src="https://agentmods.dev/badge/skills/jamiepine/voicebox/add-tts-engine.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 | $0.00056 | $0.01308 |
| Opus 5 | $0.00028 | $0.00654 |
| Sonnet 5 | $0.00011 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
add-tts-engine 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 5d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-tts-engine — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add TTS Engine
Goal
Integrate a new text-to-speech engine into Voicebox end-to-end: dependency research, backend protocol implementation, frontend UI wiring, PyInstaller bundling, and frozen-build verification. The user should only need to test the final build locally.
Reference Doc
The full phased guide lives at docs/content/docs/developer/tts-engines.mdx. Read this file in its entirety before starting. It contains:
- Phase 0: Dependency research (mandatory before writing code)
- Phase 1: Backend implementation (
TTSBackendprotocol) - Phase 2: Route and service integration (usually zero changes)
- Phase 3: Frontend integration (5 files)
- Phase 4: Dependencies (
requirements.txt, justfile, CI, Docker) - Phase 5: PyInstaller bundling (
build_binary.py+server.py) - Phase 6: Common upstream workarounds
- Implementation checklist (gate between phases)
Workflow
1. Read the guide
# Read the full TTS engines doc
cat docs/content/docs/developer/tts-engines.mdx
Internalize all phases, especially Phase 0 and Phase 5. The v0.2.3 release was three patch releases because Phase 0 was skipped.
2. Dependency research (Phase 0)
Clone the model library into a temporary directory and audit it. Do NOT skip this.
mkdir /tmp/engine-research && cd /tmp/engine-research
git clone <model-library-url>
Run the grep searches from Phase 0.2 in the guide against the cloned source and its transitive dependencies. Produce a written dependency audit covering:
- PyPI vs non-PyPI packages
- PyInstaller directives needed (
--collect-all,--copy-metadata,--hidden-import) - Runtime data files that must be bundled
- Native library paths that need env var overrides in frozen builds
- Monkey-patches needed (
torch.load, float64, MPS, HF token) - Sample rate
- Model download method (
from_pretrainedvssnapshot_download+from_local)
Test model loading and generation on CPU in the throwaway venv before proceeding.
3. Implement (Phases 1–4)
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.
- 5d ago First seen · 121 lines · 56 tokens per session scan A ac1d6d859938
add-tts-engine is a skill published in the GitHub repository jamiepine/voicebox (52,058 stars, last pushed 26d ago), licensed MIT. It adds 56 tokens to every session and 1,308 once invoked, about $0.0003 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 skills, from other repositories
videoagent-audio-studio
Tired of juggling multiple audio APIs? This skill gives you one-command access to TTS, music generation, sound effects, and voice cloning. Use when you want to generate any audio without managing multiple API keys.
transcribe-tool
Audio transcription tool. Converts audio files to text with Whisper and optional LLM post-processing. Use when: transcribing meetings, podcasts, or extracting text from recorded audio files.
audio-transcriber
Transform audio recordings into professional Markdown documentation with intelligent summaries using LLM integration.
talkthrough
Analyze narrated screen recordings and audio files — timestamped transcript, scene keyframes, OCR text, and wall-clock anchoring via the local talkthrough MCP server. Use when the user shares a recording or asks to triage feedback, extract meeting actions, or correlate a recording with logs.
transcribe-audio
Use when a task requires reading, transcribing, or extracting content from audio or voice — WhatsApp PTT/voice notes (.opus/.ogg), meeting recordings, .mp3/.m4a/.wav/.mp4 files, or audio attachments inside a WhatsApp chat-export zip.
talkthrough
Analyze narrated screen recordings and audio files through the talkthrough MCP server — triage feedback into findings, extract specs/backlogs/action items from recordings, and correlate spoken remarks with logs via wall-clock timestamps. Use when the user mentions a screen recording, screencast, narrated video/audio…