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.
npx agentmods add commands/junianwoo/claude-toad/testgit clone --depth 1 https://github.com/junianwoo/claude-toadWhat 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 | $0.00000 | $0.00173 |
| Opus 5 | $0.00000 | $0.00086 |
| Sonnet 5 | $0.00000 | $0.00035 |
| Haiku 4.5 | $0.00000 | $0.00017 |
Grade A, and why
test 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.
What it actually says
Generated by Claude Toad — Review before use
/test - Run Test Suite
Run the project test suite and report results.
Instructions
- Run the test command:
npm test
-
Wait for the full output. Do NOT interrupt the test run.
-
Report results clearly:
- Total tests passed / failed / skipped
- If there are failures, show the failing test names and error messages
- Group failures by test file if multiple files have failures
-
Do NOT auto-fix failing tests. Instead:
- Explain what each failure likely means
- Ask the user if they want you to investigate or fix specific failures
-
If the test command itself fails to run (e.g., missing dependencies, config errors), report the error and suggest how to resolve it.
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.
- 2d ago First seen · 25 lines · 0 tokens per session scan A 370042a09b55
test is a command published in the GitHub repository junianwoo/claude-toad (4 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 173 tokens. 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
verify-structure
Verify project structure aligns with official Claude Code standards.
project-status
Show current project implementation status.
plan-feature
Plan a new feature using spec-workflow-orchestrator skill.
research-topic
Research a topic using multi-agent-researcher skill.
config
Interactive configuration for claude-gauge status line.
api-docs
Launch the API documentation specialist for OpenAPI specs.