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/blencorp/claude-code-kitWrote 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/blencorp/claude-code-kit/route-research-for-testing)<a href="https://agentmods.dev/commands/blencorp/claude-code-kit/route-research-for-testing"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/route-research-for-testing/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/blencorp/claude-code-kit/route-research-for-testing"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/route-research-for-testing.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.00006 | $0.00286 |
| Opus 5.5 | $0.00002 | $0.00114 |
| Sonnet 5.5 | $0.00001 | $0.00057 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade B, and why
route-research-for-testing 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.
!cat "$CLAUDE_PROJECT_DIR/.claude/tsc-cache"/\*/edited-files.log 2>/dev/null | awk -F: '{print $2}' | grep '/routes/' | sort -u || echo "No route files modified yet" What it actually says
Context
Changed route files this session (auto-generated):
!cat "$CLAUDE_PROJECT_DIR/.claude/tsc-cache"/*/edited-files.log 2>/dev/null | awk -F: '{print $2}' | grep '/routes/' | sort -u || echo "No route files modified yet"
User-specified additional routes: $ARGUMENTS
Your task
Follow the numbered steps exactly:
- Combine the auto list with
$ARGUMENTS, dedupe, and resolve any prefixes defined insrc/app.ts. - For each final route, output a JSON record with the path, method, expected request/response shapes, and valid + invalid payload examples.
- Use the Task tool to launch the auth-route-tester agent with:
- subagent_type:
auth-route-tester - description:
route smoke tests - prompt:
Test all the routes identified above. For each route, verify it exists, test with valid authentication and payloads, test error cases, and verify database records are created correctly.
- subagent_type:
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 · 28 lines · 6 tokens per session scan B 05b561194522
route-research-for-testing is a command published in the GitHub repository blencorp/claude-code-kit (107 stars, last pushed 10mo ago), licensed MIT. It adds 6 tokens to every session and 286 once invoked, about $0.0000 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-30.
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.