Pick a model per job and degrade sensibly when one fails — a quality bar per call site, candidates compared on the same task set, a readable routing rule, and an explicit retry-versus-fallback path with pinned model ids. Use when cost or latency has become a problem, when adding a cheaper or larger model to an existing system, or when a fallback fires silently and quality drops without anyone noticing. Not for prompt authoring, not for retrieval tuning, and not for capacity or infrastructure…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Model routing
Routing is a claim that one job needs less than another. That claim is either measured or it is a
guess with a billing line attached. The expensive mistake is not picking the wrong model — it is
switching models and having no way to notice what got worse.
## When this fires
A system calls more than one model, or is about to, and someone needs to decide which call goes
where and what happens when a call fails. It also fires when a fallback exists and nobody can say
how often it triggers. It does not fire for a single call site with no cost or latency pressure —
there, one capable model and no routing layer is the correct design.
## Procedure
1. **Enumerate the jobs, not the models.** Each call site is a job with its own latency budget,
output shape, error tolerance, and whether a human sees the output before it has an effect.
Routing decisions belong per job; a single global "which model do we use" question has no
answer.
2. **Write the quality bar for each job before looking at any candidate.** What output counts as
acceptable, and how that is checked: exact match, schema validity, a rubric, a graded sample,
…
The line at the top of this page pins the label git:20260919.a0d4f55, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_4xvryyvwnbdluwjo
GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/model-routing
GET https://markdownregistry.com/api/v1/blob/66e6859df17db82f84ad236e9be15a007084ce20413991e9b54ca79aba16d4b3
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nahid-sparktales/agent-dispatcher · skills/agent-dispatcher/SKILL.md · Handle requested Agent Dispatcher work with direct execution or prepared specialist guidance. Includes named roles…
nahid-sparktales/agent-dispatcher · skills/ai/agent-design/SKILL.md · Scope an agent or subagent before it is built — the one job it owns, the smallest tool set that closes that job, what…
nahid-sparktales/agent-dispatcher · skills/ai/agent-evals/SKILL.md · Build an eval suite that can actually detect a regression — cases pulled from real traffic, graders that check…
nahid-sparktales/agent-dispatcher · skills/ai/context-engineering/SKILL.md · Decide what actually occupies the model's window — progressive disclosure through an index, retrieval versus inlining…
nahid-sparktales/agent-dispatcher · skills/ai/llm-observability/SKILL.md · See what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency…
nahid-sparktales/agent-dispatcher · skills/ai/mcp-design/SKILL.md · Build an MCP server, or bring an existing one into a project — choosing the transport, deciding which tools, resources…
nahid-sparktales/agent-dispatcher · skills/ai/memory-design/SKILL.md · Decide what an agent should remember, which layer holds it, who it is scoped to, and how a stale or contradicted memory…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-engineering/SKILL.md · Write or revise a prompt so it holds up — output contract, instruction placement, examples that earn their place, an…
nahid-sparktales/agent-dispatcher · skills/ai/prompt-injection-defense/SKILL.md · Treat everything an agent reads but did not author as data rather than instructions — an explicit trust boundary, a…
nahid-sparktales/agent-dispatcher · skills/ai/retrieval-rag/SKILL.md · Build and fix retrieval that actually returns the right passage — structure-aware chunking, one pinned embedding model…
nahid-sparktales/agent-dispatcher · skills/ai/structured-output/SKILL.md · Get parseable, trustworthy structured results out of a model — schema design, the enforcement mechanism the provider…
nahid-sparktales/agent-dispatcher · skills/ai/tool-design/SKILL.md · Design the tools a model calls — names, parameter shapes, what a result returns, and error text written as an…
frankxai/claude-skills-library · free-skills/model-routing/SKILL.md · Intelligent model selection — routes tasks to Haiku (fast/cheap), Sonnet (balanced), or Opus (complex/strategic) by…
cmc-27/pass-the-parcel · .devops/skills/model-routing/SKILL.md · Make sure to use this skill whenever the user mentions choosing a model, model selection, capability classes, binding…
noeigenstate/agentrix · skills/model-routing/SKILL.md · Who does what in this project (with a fallback table for when only Claude Code or only Codex is installed) — the lead…
noeigenstate/agentrix · resources/skills/model-routing/SKILL.md · Use before any task that changes the project, however small (a new feature or a change to one, a bug fix or debugging…
frankxai/agentic-creator-os · .claude/skills/model-routing/SKILL.md · Intelligent model selection - routes tasks to Haiku (fast/cheap), Sonnet (balanced), or Opus (complex/strategic) based…
moonray/repoprompt-workflows · .agents/skills/model-routing/SKILL.md · Use when choosing an oracle model or effort level for spec, plan, or review consultations (ask_oracle, context_builder…
naman10parikh/agentgrid · .claude/skills/model-routing/SKILL.md · Adaptive budget-aware model routing. Manages 4-tier system to maximize $200/mo Max plan usage across full weekly cycle…
yeaight7/agent-powerups · plugins/agentic-systems/skills/model-routing/SKILL.md · Use when selecting a model for a new task or subagent, deciding whether to escalate after a failed attempt, or…