A command for testing one API route, meaning one web endpoint that accepts a request and returns a response.

Use it to locate a route in the codebase, determine its method and requirements, create test cases, run authenticated and unauthenticated checks, and inspect the results.

It gives a repeatable process for checking route registration, authentication, valid and invalid inputs, permissions, edge cases, and response behavior.

test-route — Command for Claude Code by blencorp/claude-code-kit

Install

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.

Clone the repo

git clone --depth 1 https://github.com/blencorp/claude-code-kit

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/blencorp/claude-code-kit/test-route/github.svg)](https://agentmods.dev/commands/blencorp/claude-code-kit/test-route)

Your own site

<a href="https://agentmods.dev/commands/blencorp/claude-code-kit/test-route"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/test-route/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/blencorp/claude-code-kit/test-route"><img src="https://agentmods.dev/badge/commands/blencorp/claude-code-kit/test-route.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 691 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00009	$0.00691
Opus 5.5	$0.00004	$0.00276
Sonnet 5.5	$0.00002	$0.00138
Haiku 4.5	$0.00001	$0.00069

Measured 1mo ago against content hash b8a687f97067, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

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.

cli/core/commands/test-route.md · 108 lines

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:
    1. Verifying route exists and is registered
    2. Testing with valid authentication and valid payload
    3. Testing with missing/invalid fields
    4. Testing authorization (if applicable)
    5. Verifying database records are created/updated correctly
    6. Checking response status codes and body structure
    7. Providing detailed test results for each scenario
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]

Read the full file on GitHub · 108 lines

Changes

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 · 108 lines · 9 tokens per session scan A b8a687f97067

Subscribe to this mod's changes

test-route is a command published in the GitHub repository blencorp/claude-code-kit (107 stars, last pushed 10mo ago), licensed MIT. It adds 9 tokens to every session and 691 once invoked, about $0.0000 per session on Opus 5.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.

Backend and APIs Testing

test-route

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Context

Your Task

Expected Output Format

What this file has done since we first saw it

Other commands, from other repositories

cloudflare-durable-objects:setup

dare-laravel-api

ads_canonical-models-validate

load-test

apim-contract-diff

e2e