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/liortesta/clawdagent/model-routegit clone --depth 1 https://github.com/liortesta/ClawdAgentWrote 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/commands/liortesta/clawdagent/model-route)<a href="https://agentmods.dev/commands/liortesta/clawdagent/model-route"><img src="https://agentmods.dev/badge/commands/liortesta/clawdagent/model-route.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00588 |
| Opus 5 | $0.00000 | $0.00294 |
| Sonnet 5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
model-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 4d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Model Router — Agent & Model Recommendation
Analyze the current task and recommend which agent (and therefore which model tier) to use. Model is set PER AGENT in YAML frontmatter — it cannot change mid-session.
Agent → Model Mapping:
Opus Agents ($$$) — Deep Thinking
- cto — Strategic decisions, architecture oversight, ADRs
- architect — System design, API contracts, DB schemas
- security-auditor — OWASP Top 10, CVE scanning, secrets detection
- data-scientist — ML pipelines, feature engineering, data validation
- meta-agent — Creates new agents on demand
- swarm-leader — Coordinates agent teams, manages task boards
- multi-ai-orchestrator — Routes tasks, coordinates cross-model workflows
Sonnet Agents ($$) — Balanced (DEFAULT)
- qa-engineer — Tests, edge cases, 90%+ coverage
- performance-engineer — Profiling, caching, bundle size
- devops-engineer — CI/CD, Docker, K8s, monitoring
- code-reviewer — Quality, readability, code smells
- doc-writer — README, API docs, Mermaid diagrams
Haiku Agents ($) — Fast & Cheap
- model-router — Task classification, agent recommendation
Recommendation Logic:
When receiving a task, recommend the appropriate agent:
IF task involves security/auth/payments → security-auditor (opus)
IF task involves architecture/design → architect or cto (opus)
IF task failed >2 times → escalate to opus agent
IF task is testing/QA → qa-engineer (sonnet)
IF task is simple fix (<20 lines) → direct edit, no agent needed
IF task is search/navigation → no agent needed (use Glob/Grep)
ELSE → sonnet agent matching the domain
Multi-Agent Orchestration:
For complex tasks, use multiple agents in sequence:
- model-router (haiku): Classify task, recommend agents
- Sonnet agent: Implement the solution
- Opus agent: Review the implementation (if critical)
Output:
TASK: [description]
CLASSIFICATION: [category]
RECOMMENDED AGENT: [agent name]
MODEL TIER: [opus/sonnet/haiku]
REASON: [why this agent]
ALTERNATIVE: [backup agent if first fails]
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.
- 4d ago First seen · 63 lines · 0 tokens per session scan A 615aa560e7c5
model-route is a command published in the GitHub repository liortesta/ClawdAgent (11 stars, last pushed 7d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 588 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-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.