Borrowing it
Nothing to install: this file belongs to EmZod/Speak-Turbo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/EmZod/Speak-Turbo/main/AGENTS.mdgit clone --depth 1 https://github.com/EmZod/Speak-TurboWrote 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/instructions/emzod/speak-turbo/agents-md)<a href="https://agentmods.dev/instructions/emzod/speak-turbo/agents-md"><img src="https://agentmods.dev/badge/instructions/emzod/speak-turbo/agents-md.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.00768 | $0.00768 |
| Opus 5 | $0.00384 | $0.00384 |
| Sonnet 5 | $0.00154 | $0.00154 |
| Haiku 4.5 | $0.00077 | $0.00077 |
Grade A, and why
Speak-Turbo AGENTS.md 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 7d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Guidance for AI agents working on the Speak-Turbo codebase.
Using speakturbo? See SKILL.md instead.
Project Structure
speakturbo/ # Python daemon
├── daemon_streaming.py # Main FastAPI server (port 7125)
├── cli.py # Python CLI fallback
└── tests/ # pytest tests
speakturbo-cli/ # Rust CLI (primary interface)
├── Cargo.toml
└── src/main.rs # Streaming HTTP client + audio playback
Architecture
User → speakturbo (Rust) → HTTP GET /tts → daemon_streaming.py → pocket-tts → audio stream
↓
Model in memory (TTSModel)
Voice states cached
Auto-shutdown after 1hr idle
The Rust CLI exists purely for latency — it starts in ~1ms vs Python's ~100ms interpreter startup.
Single Daemon Design
There is exactly one daemon implementation: daemon_streaming.py.
- Port: 7125 (hardcoded)
- API:
GET /health,GET /tts?text=...&voice=... - Host:
127.0.0.1(localhost only, with DNS rebinding protection) - Auto-shutdown: 1 hour idle timeout
Development
# Python daemon
pip install -e .
python -m speakturbo.daemon_streaming
# Rust CLI
cd speakturbo-cli
cargo build --release
./target/release/speakturbo "test"
# Tests
pytest speakturbo/tests/ -v
Key Files
| File | Purpose |
|---|---|
daemon_streaming.py |
FastAPI app, /health and /tts endpoints |
speakturbo-cli/src/main.rs |
HTTP streaming, audio buffer, rodio playback |
cli.py |
Python CLI fallback (when Rust not available) |
SKILL.md |
User-facing documentation |
Design Decisions
- Daemon architecture: Model loading is slow (~3s). Keep it resident.
- Rust CLI: Python startup adds 100ms. Rust adds ~1ms.
- HTTP streaming: Start playback before generation completes.
- Auto-shutdown: Free memory after 1hr idle. Users don't manage daemons.
- No voice cloning: Simplicity. Use
speak(Chatterbox) for that. - Localhost-only: Daemon binds to 127.0.0.1 with DNS rebinding protection.
- Output path allowlist:
-oflag restricted to/tmp,$PWD,~/.speakturbo/by default.--allow-dirfor one-off overrides,~/.speakturbo/configfor permanent additions.
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.
- 7d ago First seen · 90 lines · 768 tokens per session scan A 03c4aadbf655
Speak-Turbo AGENTS.md is an instructions file published in the GitHub repository EmZod/Speak-Turbo (20 stars, last pushed 6mo ago), licensed MIT. It adds 768 tokens to every session, about $0.0038 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.