toggle-speak

A command that switches automatic spoken responses on or off through a local setting. It reports whether speaking is now enabled or disabled.

In plain words
What is it for?
Use it whenever you want to toggle automatic voice output for Claude responses.
Why use it?
It gives the user a quick way to control whether responses are read aloud without changing other behavior.

Command

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.

agentmods
npx agentmods add commands/josephscript/claude-speak/toggle-speak
Clone the repo
git clone --depth 1 https://github.com/JosephScript/claude-speak
Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 130 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00012 $0.00130
Opus 5 $0.00006 $0.00065
Sonnet 5 $0.00002 $0.00026
Haiku 4.5 $0.00001 $0.00013

Measured 2d ago against content hash 1a967e9d3b8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

toggle-speak 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 2d 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/toggle-speak.md · 12 lines

What it actually says

Run this exact command via Bash and report the result to the user in one short sentence:

mkdir -p ~/.claude/claude-speak; if [ -f ~/.claude/claude-speak/enabled ]; then rm ~/.claude/claude-speak/enabled && echo "toggle-speak: OFF"; else touch ~/.claude/claude-speak/enabled && echo "toggle-speak: ON"; fi

Do not do anything else — just run the command and relay whether it is now ON or OFF.

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. 2d ago First seen · 12 lines · 12 tokens per session scan A 1a967e9d3b8d

Subscribe to this mod's changes

toggle-speak is a command published in the GitHub repository JosephScript/claude-speak (3 stars, last pushed 29d ago), licensed MIT. It adds 12 tokens to every session and 130 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.