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/blencorp/claude-code-kit/test-routegit clone --depth 1 https://github.com/blencorp/claude-code-kitWhat 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.00009 | $0.00691 |
| Opus 5 | $0.00005 | $0.00345 |
| Sonnet 5 | $0.00002 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
test-route 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a QA engineer specialized in API testing and validation.
Context
Route to test: $ARGUMENTS
Your Task
Test the specified route thoroughly:
-
Route Discovery
- Find the route definition in the codebase
- Identify the HTTP method (GET, POST, PUT, DELETE, etc.)
- Locate the controller and service handlers
- Understand the expected request/response structure
-
Authentication Requirements
- Determine if route requires authentication
- Identify required permissions or roles
- Check for cookie-based auth, JWT, or other auth mechanisms
-
Create Test Plan
- Valid request scenarios
- Invalid request scenarios (missing fields, wrong types, etc.)
- Edge cases (empty values, very long strings, etc.)
- Authentication/authorization failures
-
Execute Tests
- Use the Task tool to launch the auth-route-tester agent with:
- subagent_type:
auth-route-tester - description:
test route functionality - prompt: Test the route specified in $ARGUMENTS by:
- Verifying route exists and is registered
- Testing with valid authentication and valid payload
- Testing with missing/invalid fields
- Testing authorization (if applicable)
- Verifying database records are created/updated correctly
- Checking response status codes and body structure
- Providing detailed test results for each scenario
- subagent_type:
- Use the Task tool to launch the auth-route-tester agent with:
-
Validation Checks
- Response status codes match expectations
- Response body structure is correct
- Database records created/updated properly
- Error messages are clear and helpful
- Security validations work correctly
-
Report Results
- Summary of all test scenarios
- Pass/fail status for each
- Any bugs or issues found
- Recommendations for improvements
Expected Output Format
🧪 ROUTE TEST REPORT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Route: [METHOD] [PATH]
Handler: [file:line]
Authentication: [Required/Optional/None]
TEST SCENARIOS:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
1. Valid Request
Status: ✅ PASS
Response: [status code + body summary]
2. Missing Required Field
Status: ✅ PASS
Response: 400 with validation error
3. Invalid Authentication
Status: ✅ PASS
Response: 401 Unauthorized
[... more scenarios ...]
SUMMARY:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Passed: X/Y
Failed: X/Y
Coverage: [list what was tested]
ISSUES FOUND:
- [List any bugs or problems]
RECOMMENDATIONS:
- [List improvements or missing validations]
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.
- 3d ago First seen · 108 lines · 9 tokens per session scan A b8a687f97067
test-route is a command published in the GitHub repository blencorp/claude-code-kit (101 stars, last pushed 9mo ago), licensed MIT. It adds 9 tokens to every session and 691 once invoked, about $0.0000 per session on Opus 5. 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.