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/uninstall)<a href="https://agentmods.dev/commands/chendrizzy/claude-tts/uninstall"><img src="https://agentmods.dev/badge/commands/chendrizzy/claude-tts/uninstall.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.00029 | $0.00304 |
| Opus 5 | $0.00015 | $0.00152 |
| Sonnet 5 | $0.00006 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
tts:uninstall 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 6d 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
Uninstall the claude-tts runtime (service + daemon). This does NOT remove the plugin itself — plugin removal is done through the Claude Code marketplace.
Steps:
- Stop and remove the OS service — call the platform seam:
uv run python -c "from daemon.platforms import make_platform; make_platform().uninstall_service()". On macOS this boots out and deletes the launchd plist; on Linux it runssystemctl --user disable --now claude-tts.serviceand removes the unit file. (On Windows the seam is a no-op beyond manual cleanup.) - Kill the daemon — terminate the running daemon process if present and confirm
the socket at
${CLAUDE_TTS_SOCKET:-${XDG_RUNTIME_DIR:-/tmp}/claude-tts.sock}is gone. - Optionally remove config — ask whether to delete
~/.config/claude-tts(config + logs). Confirm explicitly before any destructive deletion. If the user declines, leave it in place.
After finishing, tell the user that to also remove the plugin they should remove the
claude-tts marketplace/plugin in Claude Code. Do not hardcode absolute personal
paths.
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.
- 6d ago First seen · 26 lines · 29 tokens per session scan A e1fa0a42ee9e
tts:uninstall is a command published in the GitHub repository chendrizzy/claude-tts (1 stars, last pushed 20d ago), licensed MIT. It adds 29 tokens to every session and 304 once invoked, about $0.0001 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-seed
Seed WordPress content from demo HTML — parses sections, creates pages, imports media, populates ACF fields, builds menus, supports bilingual content.
wp-audit
Comprehensive audit — security, SEO, accessibility, performance, best practices.
wp-tailwindify
Convert an HTML/CSS demo to Tailwind-native HTML — preserves section delimiters, maps colors to @theme variables.
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.
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.
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.