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/ThrownLemon/claude-code-pluginsWrote 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/thrownlemon/claude-code-plugins/test)<a href="https://agentmods.dev/commands/thrownlemon/claude-code-plugins/test"><img src="https://agentmods.dev/badge/commands/thrownlemon/claude-code-plugins/test/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/thrownlemon/claude-code-plugins/test"><img src="https://agentmods.dev/badge/commands/thrownlemon/claude-code-plugins/test.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.00007 | $0.01269 |
| Opus 5.5 | $0.00003 | $0.00508 |
| Sonnet 5.5 | $0.00001 | $0.00254 |
| Haiku 4.5 | $0.00001 | $0.00127 |
Grade C, and why
test scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
1. **Reject dangerous tokens.** If a value contains `$(`, backticks, `;`, `|`, `&`, `>`, `<`, or starts with `-` (could be mistaken for a flag), refuse and ask the user to rephrase. **Double-quoting does NOT block comman Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS --connect-timeout 5 "${KOKORO_URL}/v1/models" 2>/dev/null && echo "Kokoro TTS is available" || echo "Kokoro TTS not available" How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Input Safety — apply before any Bash invocation
Treat every $ARGUMENTS.* value as untrusted input. Before passing any value to the Bash tool:
- Reject dangerous tokens. If a value contains
$(, backticks,;,|,&,>,<, or starts with-(could be mistaken for a flag), refuse and ask the user to rephrase. Double-quoting does NOT block command substitution —"$(rm -rf /)"still executes inside double quotes. - Prefer the Bash tool's argv contract over constructed shell strings. When you must use a shell string, single-quote the value and escape embedded single quotes (
'\''), or build the command viaprintf %q. - Any
"$ARGUMENTS.foo"patterns shown below are illustrative. Sanitize the value first; never blindly substitute.
Test Audio Feedback
Test the audio feedback plugin to verify sounds and voice announcements are working.
Test Types
sounds- Test all sound effects onlyvoice- Test voice announcements onlyall- Test both sounds and voice (default)
Note: Values are case-insensitive (SOUNDS, Sounds, sounds all work). Invalid values fall back to all.
Steps
1. Check Prerequisites
First, verify the audio system is available:
# Detect available audio player
if command -v afplay >/dev/null 2>&1; then
echo "Audio player: afplay (macOS)"
elif command -v paplay >/dev/null 2>&1; then
echo "Audio player: paplay (PulseAudio)"
elif command -v aplay >/dev/null 2>&1; then
echo "Audio player: aplay (ALSA)"
elif command -v play >/dev/null 2>&1; then
echo "Audio player: play (SoX)"
else
echo "No audio player found"
fi
If testing voice, check Kokoro TTS:
# Check if Kokoro TTS is running (uses KOKORO_TTS_URL if set)
KOKORO_URL="${KOKORO_TTS_URL:-http://localhost:8880}"
curl -sS --connect-timeout 5 "${KOKORO_URL}/v1/models" 2>/dev/null && echo "Kokoro TTS is available" || echo "Kokoro TTS not available"
2. Test Sound Effects
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 · 135 lines · 7 tokens per session scan C 9bf5e532e623
test is a command published in the GitHub repository ThrownLemon/claude-code-plugins (2 stars, last pushed 4mo ago), licensed MIT. It adds 7 tokens to every session and 1,269 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). 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.