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/chendrizzy/claude-ttsWrote 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/chendrizzy/claude-tts/doctor)<a href="https://agentmods.dev/commands/chendrizzy/claude-tts/doctor"><img src="https://agentmods.dev/badge/commands/chendrizzy/claude-tts/doctor/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/commands/chendrizzy/claude-tts/doctor"><img src="https://agentmods.dev/badge/commands/chendrizzy/claude-tts/doctor.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.00042 | $0.00671 |
| Opus 5 | $0.00021 | $0.00336 |
| Sonnet 5 | $0.00008 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
Grade A, and why
tts:doctor 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.
What it actually says
Diagnose the claude-tts installation. This command is idempotent — safe to run anytime, changes nothing. For each check print PASS or WARN and, on WARN, exactly one remediation.
Checks:
- Disk — free space on the volume holding the audio temp directory. WARN if low; below ~200 MB free the daemon's disk guard evicts cache, refuses to synthesize, and fires a loud desktop + statusline alert (it no longer silently mutes).
- Daemon process + socket — is the daemon process alive AND is the socket bound
at
${CLAUDE_TTS_SOCKET:-${XDG_RUNTIME_DIR:-/tmp}/claude-tts.sock}? WARN if the process is up but the socket is missing (a stale/orphaned daemon), with a restart remediation. - Python deps — are the daemon's required Python packages importable in its environment? WARN with the install command if any are missing.
- Backend reachability — for the configured backend, confirm it is reachable: Ollama responding, the Voicebox app running, or edge-tts network access. WARN with how to start/restore the backend.
- Summarizer budget vs. inner timeout (Ollama LLM path only) — read
summarizer.soft_tokens(default 200) andslack_tokens(default 96) → the hard generation ceilingnum_predict = soft + slack(default 296), andsummarizer.inner_timeout_s(default 5.0). A full-budget summary must finish within the inner timeout or it falls back to the deterministic rule-based summary. If Ollama is reachable, time a small generation (num_predict: 64) against the configured model and derive tokens/sec from the response'seval_count/eval_duration; WARN ifinner_timeout_s < (num_predict / tok_per_sec) × 1.3(a full-budget summary risks timing out) — remediation: raiseinner_timeout_s, or lowersoft_tokens/slack_tokens. Report the numbers either way (e.g. "budget 296 tok ≈ 1.9 s at ~155 tok/s vs 5.0 s timeout — OK"). The bundled defaults pass with margin at normal speeds; this mainly catches a budget raised past its timeout, or a host too slow for the configured budget. If throughput can't be measured, only WARN when the budget exceeds 296 while the timeout is still ≤ 5.0 s.
After all checks, print a one-line overall verdict (all PASS, or the count of WARNs).
Do not hardcode absolute personal paths; read locations from ~/.config/claude-tts
and the XDG socket expression above.
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 · 43 lines · 42 tokens per session scan A 618b87128754
tts:doctor is a command published in the GitHub repository chendrizzy/claude-tts (1 stars, last pushed 22d ago), licensed MIT. It adds 42 tokens to every session and 671 once invoked, about $0.0002 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-31.
Other commands, from other repositories
wp-debug
Diagnose WordPress issues — runs health checks, identifies problems, and offers WP-CLI fixes.
debug-helper
Use when something is broken and you need it diagnosed. A build failure, a runtime crash, a blank page, an unreadable error message, or behaviour that is simply wrong. Gives one exact fix, not a list of things to try.
error-handling-specialist
Use when things go wrong badly. Error messages that blame the user, validation firing at the wrong moment, form data lost on failure, dead-end 404 and 500 pages, or no way to retry.
linkerd
Linkerd-specific diagnostics — mTLS verification, proxy injection issues, authorization policy debugging, traffic management, and multi-cluster connectivity problems.
wp-tailwindify
Convert an HTML/CSS demo to Tailwind-native HTML — preserves section delimiters, maps colors to @theme variables.
ia-report-bug
Report a bug in the whetstone plugin.