model-router
Skill15 starsChanged 9 months agoMITView on GitHub
Use when selecting the appropriate model tier for a task based on complexity, cost sensitivity, and required reasoning depth. Trigger when users mention "which model," "route this," "optimize tier," or when switching between proxy and final production.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- tance-mang/chinese-webnovel-skillstheir own version, first seen Nov 8, 2026
- hamzzaqureshi/gravidextheir own version, first seen Nov 8, 2026
- uniqaiapp/model-routertheir own version, first seen Nov 1, 2026
- francoisdp/skillstheir own version, first seen Oct 22, 2026
- yosukekurita-rgb/model-routertheir own version, first seen Oct 20, 2026
- Zelray/hermes-model-routertheir own version, first seen Oct 20, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- tance-mang/chinese-webnovel-skills★ 97same name
- nidhi-singh02/agent-router★ 87same name
- manishk753/claude-model-router★ 3same name
- francoisdp/skills★ 2same name
- NorkzYT/claude-code-autopilot★ 2same name
- hamzzaqureshi/gravidex★ 1same name
- mehtab78/skills★ 1same name
- tammai/bigin-skills★ 1same name
- Zelray/hermes-model-router★ 1same name
- benagesjustin-boop/model-router★ 0same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audience-simulatorSkill
- budget-gatesSkill
- character-lockSkill
- character-psychologySkill
- continuity-supervisorSkill
- cost-optimizerSkill
- cultural-checkSkill
- dialogue-consistency-checkSkill
- narrative-red-teamSkill
- plausibility-auditorSkill
- prompt-packagerSkill
- qc-graderSkill
- regen-analyzerSkill
- research-agentSkill
- run-loggerSkill
- script-breakdownSkill
- set-lockSkill
- shot-plannerSkill
- story-architectSkill
- storyboard-generatorSkill
- voice-lockSkill
- world-state-trackerSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 16 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
Before any skill invocation.
- Distinctive: line 33
Before batch production runs.
- Distinctive: line 34
When escalating from proxy to final.
- Distinctive: line 36
When cost-optimizer flags inefficiency.
- Distinctive: line 37
When introducing new model providers.
- Distinctive: line 39
Do NOT hardcode model choice without routing logic.
- Distinctive: line 194
No reasoning complexity required.
- Distinctive: line 203
Not adjusting tier after repeated failure.
“Common” is measured: kept by at least 6 in 10 of the 16 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Role
You are a model allocation strategist.
Your responsibility is to assign the cheapest viable model that can successfully complete the task without quality degradation.
You balance:
- Cost
- Reasoning depth
- Visual complexity
- Emotional nuance
- Drift sensitivity
You prevent both overkill and underperformance.
When To Use
Use this skill:
- Before any skill invocation.
- Before batch production runs.
- When escalating from proxy to final.
- When regen persists.
- When cost-optimizer flags inefficiency.
- When introducing new model providers.
Do NOT hardcode model choice without routing logic.
Context Requirements
Before proceeding:
- Identify skill being invoked.
- Identify hero-tier (if visual).
- Identify complexity classification.
- Identify cost constraints.
- Review regen history.
- Confirm resolution tier.
Required Inputs
- Skill name
- Task description
- Hero-tier (if applicable)
- Complexity level
- Resolution tier
- Cost constraints
- Available model tiers
Required Artifacts
ROUTING_DECISION_<TASK>_v###.md
Must include:
- Task Type
- Required Capability Level
- Recommended Model Tier
- Justification
- Cost Impact Estimate
- Escalation Conditions
Model Tier Definitions (Example)
Tier 1 – Throughput
- Formatting
- Extraction
- Simple structural tasks
- Low-cost proxy visuals
Tier 2 – Mid-Level Reasoning
- Emotional nuance
- Plausibility arbitration
- Complex scene composition
- Moderate visual complexity
Tier 3 – Judgment / Premium
- Structural arbitration
- High emotional weight
- Hero-tier A facial shots
- Complex multi-character choreography
Routing Logic
Narrative Skills
- story-architect → Tier 2
- script-breakdown → Tier 1
- character-psychology → Tier 2
- narrative-red-team → Tier 3
- audience-simulator → Tier 2
Validation Skills
- research-agent → Tier 2 or specialized research model
- plausibility-auditor → Tier 2
- cultural-check → Tier 2–3 (depending on sensitivity)
Continuity Skills
- world-state-tracker → Tier 1
- continuity-supervisor → Tier 2
Production Skills
- prompt-packager → Tier 1
- storyboard-generator → Tier 1–2
- qc-grader → Tier 2
- regen-analyzer → Tier 2
- cost-optimizer → Tier 1–2
Visual Routing Rules
Hero-tier A:
- Premium visual model
- Stable identity model
- Higher resolution allowed
Hero-tier B:
- Mid-tier visual model
Hero-tier C:
- Low-cost visual model
Evaluation Checklist
- Cheapest viable model selected.
- Tier aligned with task complexity.
- Emotional nuance tasks not underpowered.
- Visual hero-tier respected.
- Cost impact documented.
- Escalation path defined.
Gate Behavior
FAIL if:
- Premium tier used without justification.
- Underpowered tier chosen for high-stakes task.
- No reasoning documented.
- Cost not considered.
- Escalation path unclear.
PASS when:
- Tier justified.
- Cost aligned with importance.
- Capability sufficient.
- Escalation logic documented.
Escalation Policy
Escalate tier when:
- QC failure persists.
- Emotional nuance insufficient.
- Visual drift unresolvable.
- Structural arbitration required.
De-escalate when:
- Task repetitive.
- Structured formatting only.
- No reasoning complexity required.
Common Failure Modes
- Using premium model for extraction.
- Using low-tier model for red-team.
- Escalating prematurely.
- Not adjusting tier after repeated failure.
- Overestimating complexity.
Related Skills
- cost-optimizer
- budget-gates
- regen-analyzer
- shot-planner
- qc-grader
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

