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/TwinPeaksTownie/Claude-to-SpeechWrote 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/twinpeakstownie/claude-to-speech/explain-more)<a href="https://agentmods.dev/commands/twinpeakstownie/claude-to-speech/explain-more"><img src="https://agentmods.dev/badge/commands/twinpeakstownie/claude-to-speech/explain-more/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/twinpeakstownie/claude-to-speech/explain-more"><img src="https://agentmods.dev/badge/commands/twinpeakstownie/claude-to-speech/explain-more.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.00008 | $0.01308 |
| Opus 5 | $0.00004 | $0.00654 |
| Sonnet 5 | $0.00002 | $0.00262 |
| Haiku 4.5 | $0.00001 | $0.00131 |
Grade C, and why
explain-more scanned grade C with 1 finding 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 12d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- TTS: "Memory usage grows until crash after 6 hours. Event listeners aren't cleaned up when users disconnect, so the listener arrays grow indefinitely and hold references to user objects. This prevents garbage collec How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are now in explain-more mode - provide deep analysis of the problem we're facing.
When to Use Two-Response Protocol
ONLY use the two-response interruption protocol if you were actively working on something.
If Interrupted Mid-Work:
First Response: Acknowledgment (TTS-only, NO TOOLS)
<!-- TTS: "OK, I'm stopping. Is there something we need to change?" -->
or
<!-- TTS: "I was about to implement the validation logic. What's up?" -->
or
<!-- TTS: "I just finished the auth refactor but it looks like you want to talk, what do you need?" -->
Second Response: Wait for user to tell you what needs deeper explanation, then provide your two-paragraph analysis.
If Already in Conversation (Not Mid-Work):
Just acknowledge the mode switch and wait:
<!-- TTS: "Switching to explain-more mode" -->
or just use <!-- TTS: SILENT --> and wait for the user to specify what to explain in depth.
IMPORTANT: Acknowledgment responses must:
- Contain ONLY a TTS marker (and minimal text if needed)
- Use NO TOOLS whatsoever
- The TTS hook only works on responses without tool calls
Response Format: 70 Words Total
Two paragraphs, about 70 words total:
- Paragraph 1: What's happening and why it matters
- Paragraph 2: Root cause, context, and relevant question
- Stay focused and concise
- End with a meaningful question
NO CODE Solutions
Do NOT provide:
- Code examples
- Implementation details
- Specific function signatures
- File paths for where to make changes
Focus on:
- Understanding the problem
- Explaining the architecture
- Discussing tradeoffs
- Asking meaningful questions
The Question: Must Be RELEVANT
The question at the end MUST represent a meaningful choice for the user.
Good questions (represent real choices):
- "Do you want to prioritize speed or accuracy here?"
- "Should we handle this error gracefully or fail fast to make debugging easier?"
- "Do you want to fix this at the database level or in the application layer?"
- "Should we maintain backward compatibility or break the API to fix this properly?"
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.
- 12d ago First seen · 134 lines · 8 tokens per session scan C 603a20a48607
explain-more is a command published in the GitHub repository TwinPeaksTownie/Claude-to-Speech (19 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 1,308 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
report
Generate a project analytics report covering code quality, velocity, and health metrics.
explain
Explain a code file, function, or concept in clear, structured language.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.
document-all
Auto-document the entire codebase by generating module-level docs, function signatures, and API references.
fix-comments
Address PR review comments by implementing requested changes automatically.
write-post
Write a technical blog post with a clear structure, code examples, and actionable takeaways.