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/JosephScript/claude-speakWrote 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/josephscript/claude-speak/speak-limit)<a href="https://agentmods.dev/commands/josephscript/claude-speak/speak-limit"><img src="https://agentmods.dev/badge/commands/josephscript/claude-speak/speak-limit/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/josephscript/claude-speak/speak-limit"><img src="https://agentmods.dev/badge/commands/josephscript/claude-speak/speak-limit.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.00018 | $0.00268 |
| Opus 5.5 | $0.00007 | $0.00107 |
| Sonnet 5.5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade B, and why
speak-limit scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- **No argument**: report the current limit. Run `cat ~/.claude/claude-speak/limit 2>/dev/null`; if empty/missing, the limit is the default (2000 bytes). What it actually says
Based on the argument passed to this command, do exactly one of the following via Bash, then report the result in one short sentence — nothing else:
- No argument: report the current limit. Run
cat ~/.claude/claude-speak/limit 2>/dev/null; if empty/missing, the limit is the default (2000 bytes). - A positive integer (e.g.
1200): set that as the new limit:mkdir -p ~/.claude/claude-speak && echo <number> > ~/.claude/claude-speak/limit. reset: clear back to the default:rm -f ~/.claude/claude-speak/limit.- Anything else: don't write anything — tell the user the argument wasn't understood (must be a positive integer or
reset).
This limit applies everywhere the mechanical formatter runs: the automatic /toggle-speak Stop hook and /speak (local mode). It has no effect on /speak llm, whose length is controlled by the model's own summarization instead of this cap.
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 · 14 lines · 18 tokens per session scan B ab2500e2775c
speak-limit is a command published in the GitHub repository JosephScript/claude-speak (4 stars, last pushed 2mo ago), licensed MIT. It adds 18 tokens to every session and 268 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
config
Configure iterm2-tab-status plugin settings (emoji prefixes, colors, display target, subtitle activity, badge, notifications).
run
A command that starts a planned, isolated Windows computer-use task. It follows prepared steps, checks the computer setup, uses screenshots when needed, and reports what was actually verified.
doctor
A command that diagnoses the Computer Use plugin, its environment, and its mapped capabilities. Computer Use lets an agent interact with a computer through supported actions.
trace
A command for viewing or exporting privacy-filtered Computer Use activity traces. A trace is a record of actions taken during a computer-use session, and the command supports status, listing recent traces, and confirmed export.
benchmark
A command that produces a report measuring Computer Use capabilities, such as task completion and tool activity. Computer Use means controlling applications through an interactive computer interface.
test
A command for running general capability tests for computer-use features, which let an agent interact with supported computer applications. It uses a quick test by default and does not operate real user applications.