catalyst: Command for Claude Code

.claude/commands/route-research-for-testing.md

route-research-for-testing is a command for Claude Code from dwalleck/catalyst. It costs 6 tokens per session (258 once invoked), scanned B, original, MIT.

A command that finds changed web routes, combines them with any routes you name, and prepares structured test cases for each one. A route is a URL path that an application handles, such as an account or checkout endpoint.

In plain words
What is it for?
Use it after route changes to list each route’s method, request and response format, and example payloads. It then asks a testing sub-agent to run route smoke tests.
Why use it?
It reduces the manual work of finding which endpoints changed and deciding how to test them. It also helps keep valid and invalid request examples together for follow-up smoke tests.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; mentions subagents; positional $N argument.

This is dwalleck/catalyst's own configuration. It tells Claude Code how to work on catalyst itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything catalyst configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dwalleck/catalyst. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dwalleck/catalyst/main/.claude/commands/route-research-for-testing.md
Clone the repo
git clone --depth 1 https://github.com/dwalleck/catalyst

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.

agentmods badge for route-research-for-testing

README.md
[![agentmods](https://agentmods.dev/badge/commands/dwalleck/catalyst/route-research-for-testing.svg)](https://agentmods.dev/commands/dwalleck/catalyst/route-research-for-testing)
Your own site
<a href="https://agentmods.dev/commands/dwalleck/catalyst/route-research-for-testing"><img src="https://agentmods.dev/badge/commands/dwalleck/catalyst/route-research-for-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 258 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00006 $0.00258
Opus 5 $0.00003 $0.00129
Sonnet 5 $0.00001 $0.00052
Haiku 4.5 $0.00001 $0.00026

Measured 6d ago against content hash 45fd17c69da2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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 6d 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 \
.claude/commands/route-research-for-testing.md · 38 lines

What it actually says

Context

Changed route files this session (auto-generated):

!cat "$CLAUDE_PROJECT_DIR/.claude/tsc-cache"/*/edited-files.log
| awk -F: '{print $2}'
| grep '/routes/'
| sort -u

User-specified additional routes: $ARGUMENTS

Your task

Follow the numbered steps exactly:

  1. Combine the auto list with $ARGUMENTS, dedupe, and resolve any prefixes defined in src/app.ts.
  2. For each final route, output a JSON record with the path, method, expected request/response shapes, and valid + invalid payload examples.
  3. Now call the Task tool using:
{
    "tool": "Task",
    "parameters": {
        "description": "route smoke tests",
        "prompt": "Run the auth-route-tester sub-agent on the JSON above."
    }
}
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.

  1. 6d ago First seen · 38 lines · 6 tokens per session scan B 45fd17c69da2

Subscribe to this mod's changes

route-research-for-testing is a command published in the GitHub repository dwalleck/catalyst (11 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 258 once invoked, about $0.0000 per session on Opus 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.