agentmods.dev

tts:setup

tts:setup is a command for Claude Code from chendrizzy/claude-tts. It costs 33 tokens per session (844 once invoked), scanned A, original, MIT.

A first-run setup command for claude-tts, a system that reads coding-agent responses aloud. It configures the speech engine, language-model backend, settings, and background service.

In plain words
What is it for?
It helps choose voices and voice policies, configure the processing backend, install the operating-system service, and verify that the daemon starts.
Why use it?
It brings the required components together so text-to-speech can start and continue running in the background.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents; mentions Claude Code.

Part of the claude-tts plugin — 1 skill, 8 commands, 5 hooks shipped together

not rated 1repo 12d ago A scan 33 tokens original MIT

Good fit It helps choose voices and voice policies, configure the processing backend, install the operating-system service, and verify that the daemon starts.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/chendrizzy/claude-tts/setup
View source ↗ chendrizzy/claude-tts dev.to
Install

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.

Clone the repo
git clone --depth 1 https://github.com/chendrizzy/claude-tts

Made for: Claude Code.

Or install claude-tts, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 5 hooks.

Wrote 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.

agentmods badge for tts:setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/chendrizzy/claude-tts/setup/github.svg)](https://agentmods.dev/commands/chendrizzy/claude-tts/setup)
Your own site
<a href="https://agentmods.dev/commands/chendrizzy/claude-tts/setup"><img src="https://agentmods.dev/badge/commands/chendrizzy/claude-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.

agentmods 80×15 button for tts:setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/chendrizzy/claude-tts/setup"><img src="https://agentmods.dev/badge/commands/chendrizzy/claude-tts/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 844 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00033 $0.00844
Opus 5.5 $0.00013 $0.00338
Sonnet 5.5 $0.00007 $0.00169
Haiku 4.5 $0.00003 $0.00084

Measured 1mo ago against content hash e29420c94027, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 1mo 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.

commands/setup.md · 59 lines

What it actually says

You are running first-run setup for the claude-tts plugin.

Invoke the tts-setup skill and follow it end-to-end. The skill bootstraps:

  1. Detect the platform and architecture (macOS/Linux, arm64/x86_64).
  2. Ensure uv and a project virtual environment are available.
  3. Pick the speech engine.
  4. Ask whether voices vary per project or stay shared across all projects.
  5. Ask for voice gender policy: balanced, female-only, male-only, mostly female, or mostly male. The stable config values are balanced, female_only, male_only, female_preferred, and male_preferred; mostly means 80/20.
  6. Pick the LLM backend for content routing.
  7. Calibrate the chosen backend against the bundled mini-eval.
  8. Install the OS background service (launchd on macOS, systemd --user on Linux).
  9. Write ~/.config/claude-tts/config.json.
  10. Verify the daemon starts and the socket binds at ${CLAUDE_TTS_SOCKET:-${XDG_RUNTIME_DIR:-/tmp}/claude-tts.sock}.

Run the skill now. Do not hardcode absolute paths — always use ~/.config/claude-tts and the XDG socket expression above. If a step cannot complete, report which step failed and the single most likely remediation, then stop.

Note: the full bootstrap and calibration logic lives in the tts-setup skill. If the skill reports it is a stub, tell the user setup automation is not yet available in this build and point them at /tts:doctor to check current health.

Only edge-tts and kokoro expose bundled gender metadata in this plugin. For say, espeak, and voicebox, setup must keep project_voices.enabled=false and explain that gender/per-project assignment is not enforceable for that engine. Changing a generated voice pool can remap projects, so restart the daemon after changing these preferences.

Optional post-setup integrations (not part of the automated skill flow):

  • Cursor editor. To drive TTS from Cursor too, manually wire the three cursor-*.sh hooks (cursor-pre-tool-use.sh, cursor-post-tool-use.sh, cursor-after-agent-response.sh) into Cursor's hook config — they are not registered in hooks/hooks.json, so Claude Code never loads them. They map Cursor's preToolUse/postToolUse/afterAgentResponse events onto the Claude Code hooks with CLAUDE_TTS_PASSTHROUGH=false (the gate defaults to true; setting it false keeps Cursor's stdout clean). On macOS the after-response hook uses GNU timeout — brew install coreutils. Knobs: CLAUDE_TTS_ENABLED, CLAUDE_TTS_PYTHON, CLAUDE_TTS_PASSTHROUGH. See the Cursor section of the README for the full steps.

  • 🔊 statusline segment. Everything spoken is logged to a bounded per-session JSONL (~/.claude/logs/tts/spoken/<session>.jsonl), readable with /tts:log; sub-agents and background-agents each get their own session file. The statusline config block (subagent_aware, active_window_s, include_subagent_in_main) is VIEW-ONLY — it tunes what that view shows, not what the daemon logs. The repo ships the config block and the spoken log; the wrapper that renders the live 🔊 segment in your statusline is a personal/global file and is not shipped here.

Changes

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.

  1. 1mo ago First seen · 59 lines · 33 tokens per session scan A e29420c94027

Subscribe to this mod's changes

tts:setup is a command published in the GitHub repository chendrizzy/claude-tts (1 stars, last pushed 12d ago), licensed MIT. It adds 33 tokens to every session and 844 once invoked, about $0.0001 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-08-31.

Claude Codeaccessibilityai-agentclaude-code-pluginkokorolocal-llm
Related

Other commands, from other repositories

anti-slop-designer

Use when a UI looks machine-made rather than decided. Violet gradients, glassmorphism everywhere, identical cards in a grid, untouched shadcn or Material defaults, emoji bullets, or copy stuffed with seamless and unlock.

imsaif/design-with-claude · 44 tokens

design-enforce

Use when code has drifted off the design system. Raw hex values and pixel numbers written where a token already exists, one-off components, library defaults left untouched. Finds every bypass and fixes it.

imsaif/design-with-claude · 40 tokens

design-grill

Use when a design keeps getting reinvented every session. Interviews you until you share one understanding, then writes the vocabulary and the binding decisions into the repo so they survive the next context window.

imsaif/design-with-claude · 38 tokens

design-triage

Use when a dwic audit report is full of findings and there is no plan. Ranks them into an order someone can work through, then works through it.

imsaif/design-with-claude · 33 tokens

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.

imsaif/design-with-claude · 49 tokens

database-setup

Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.

imsaif/design-with-claude · 36 tokens