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/justdvp/claude-code-templates/routegit clone --depth 1 https://github.com/Justdvp/claude-code-templatesWhat 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.00555 |
| Opus 5 | $0.00000 | $0.00278 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- route — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Route Creator
Create API routes for $ARGUMENTS following project conventions.
Task
Create or optimize API routes based on the requirements:
- Analyze project structure: Check existing route patterns, folder organization, and framework setup
- Examine framework: Identify if using Express, Fastify, NestJS, or other Node.js framework
- Review existing routes: Understand current routing patterns, validation, and error handling
- Check authentication: Review existing auth middleware and protection patterns
- Define route structure: Determine HTTP methods, path parameters, and request/response schemas
- Implement routes: Create route handlers with proper validation and error handling
- Add middleware: Include authentication, validation, and logging middleware as needed
- Create tests: Write route tests following project testing patterns
- Update route registration: Integrate new routes into main router configuration
Implementation Requirements
- Follow project's routing architecture and naming conventions
- Use existing validation libraries (Joi, Zod, class-validator, etc.)
- Include proper TypeScript types for request/response objects
- Add comprehensive error handling with appropriate HTTP status codes
- Implement proper authentication/authorization if required
- Follow RESTful conventions unless project uses different patterns
- Add proper logging and monitoring integration
Route Patterns to Consider
Based on the request:
- CRUD operations: Create, Read, Update, Delete for resources
- RESTful endpoints: GET, POST, PUT, PATCH, DELETE with proper semantics
- Nested resources: Parent/child resource relationships
- Batch operations: Bulk create, update, delete operations
- Search/filtering: Query parameters for filtering and pagination
- File uploads: Multipart form handling for file operations
- Webhook endpoints: External service integration points
Framework-Specific Implementation
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 · 57 lines · 0 tokens per session scan A efa9e942d221
route is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 555 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
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.
migrate-pipeline
Migrate an existing pre-v2 per-tier pipeline (.claude/, .opencode/, .agents/codex/) into the unified data-only .superpipelines/ layout — select legacy pipeline, translate frontmatter to canonical agent defs, stage, delta-audit, gate on human approval, then atomically promote, rewrite the registry, and move the legacy…
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
new-pipeline
Design and scaffold a new named multi-agent pipeline with git preflight, scope selection, pre-gate audit, and entry-skill generation.
new-step
Add a new step to an existing pipeline — select pipeline, choose insertion point, design component, audit the delta, then gate on human approval.