Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add signalcompose/claude-tools/plugin install cviWrote 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/signalcompose/claude-tools/voice)<a href="https://agentmods.dev/commands/signalcompose/claude-tools/voice"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/voice/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/signalcompose/claude-tools/voice"><img src="https://agentmods.dev/badge/commands/signalcompose/claude-tools/voice.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.00005 | $0.00423 |
| Opus 5.5 | $0.00002 | $0.00169 |
| Sonnet 5.5 | $0.00001 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00042 |
Grade A, and why
voice 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.
What it actually says
CVI Voice Selection
CVI（Claude Voice Integration）の音声を設定します。
以下のBashコマンドを即座に実行してください（確認ダイアログなし）:
bash ${CLAUDE_PLUGIN_ROOT}/scripts/cvi-voice $ARGUMENTS
引数
- （引数なし） - 現在の設定を確認
en [VOICE]- 英語音声を設定ja [VOICE]- 日本語音声を設定mode auto- 自動音声選択モード（デフォルト）mode fixed- 固定音声モードfixed [VOICE]- 全言語で使用する音声を設定list- 利用可能な音声一覧reset- デフォルトに戻す
人気の音声
日本語
- system: システムデフォルト（日本語Siri）
- Kyoko: 標準日本語音声（女性）
- Otoya: 標準日本語音声（男性）
英語
- system: システムデフォルト（英語Siri）
- Samantha (US): 標準的でクリアな女性の声
- Zoe (UK): プレミアム女性音声
- Daniel (UK): イギリス英語、男性
使用例
/cvi:voice- 現在の設定を確認/cvi:voice en Zoe- 英語音声をZoeに設定/cvi:voice ja Kyoko- 日本語音声をKyokoに設定/cvi:voice list- 利用可能な音声一覧
実行後、結果を報告してください。
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.
- 1mo ago First seen · 47 lines · 5 tokens per session scan A b773e5393245
voice is a command published in the GitHub repository signalcompose/claude-tools (4 stars, last pushed 1mo ago), licensed MIT. It adds 5 tokens to every session and 423 once invoked, about $0.0000 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.