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/claude-market/marketplaceWrote 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/agents/claude-market/marketplace/router-builder)<a href="https://agentmods.dev/agents/claude-market/marketplace/router-builder"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/router-builder/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/agents/claude-market/marketplace/router-builder"><img src="https://agentmods.dev/badge/agents/claude-market/marketplace/router-builder.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.00013 | $0.00500 |
| Opus 5 | $0.00006 | $0.00250 |
| Sonnet 5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
router-builder 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 10d 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.
What it actually says
Router Builder Agent
You create the main Axum router by wiring together all handler functions with their routes.
Your Task
Given:
- List of handlers with their paths, methods, and handler function names
- Handler module names
Generate the router configuration.
Router Pattern
use axum::{
routing::{get, post, put, delete},
Router,
};
mod handlers;
use handlers::{users, orders};
pub fn create_router(state: AppState) -> Router {
Router::new()
// Health checks
.route("/health", get(health_check))
.route("/ready", get(readiness_check))
// API routes
.route("/api/users",
get(users::list_users)
.post(users::create_user))
.route("/api/users/:id",
get(users::get_user)
.put(users::update_user)
.delete(users::delete_user))
.route("/api/orders",
get(orders::list_orders)
.post(orders::create_order))
// Middleware
.layer(create_cors())
.layer(create_trace_layer())
.layer(axum::middleware::from_fn(correlation_id_middleware))
// State
.with_state(state)
}
Multiple Methods on Same Route
When multiple handlers share the same path:
.route("/api/users",
get(list_users)
.post(create_user))
Path Parameters
Use :param syntax:
.route("/api/users/:id", get(get_user))
.route("/api/users/:id/orders", get(get_user_orders))
Middleware Order
Apply middleware in this order (bottom to top execution):
.layer(create_cors()) // CORS headers
.layer(create_trace_layer()) // Request logging
.layer(timeout_middleware) // Timeouts
.layer(correlation_id_middleware) // Correlation IDs
.layer(rate_limiter) // Rate limiting
Access Skills
axum-patterns- Router and middleware patternsaxum-middleware- Middleware configurationaxum-tracing- Correlation ID middlewareaxum-health-shutdown- Health check endpoints
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.
- 10d ago First seen · 95 lines · 13 tokens per session scan A dd895dbe2aed
router-builder is an agent published in the GitHub repository claude-market/marketplace (22 stars, last pushed 10mo ago), licensed MIT. It adds 13 tokens to every session and 500 once invoked, about $0.0001 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 agents, from other repositories
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
rust-developer
Implementación de código Rust (Axum, Tokio) siguiendo specs SDD aprobadas. Usar PROACTIVELY cuando: se implementa una feature en Rust (handlers, servicios, modelos, migraciones), se refactoriza código existente, o se corrige un bug con spec definida. SIEMPRE requiere una Spec SDD aprobada antes de empezar.
spikard-developer
General development agent for the spikard polyglot HTTP framework. Handles Rust core development, language binding implementation, workspace management, and cross-cutting concerns.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
rust-expert
Use when: Cargo.toml present. Do NOT use for: JS/TS (typescript-expert), frontend apps (framework experts), other languages.