CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

model-routing

9-tier model routing system with cascading classifier fallback and result auto-evaluation

53

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/model-routing/SKILL.md
SKILL.md
Quality
Evals
Security

Model Routing System

How Routing Decisions Are Made

Every user prompt goes through a 9-tier classification pipeline before any AI model processes it. The system answers three questions:

  1. Which model should handle this? — 9-tier cost/complexity classification
  2. Is the classifier itself working? — Cascading fallback (qwen3 → kimi → deepseek → cache)
  3. Can we verify the result? — Tool-level fallback + auto-evaluation

The Pipeline

User types prompt
    ↓
UserPromptSubmit hook fires (~/.claude/hooks/route-task-hook)
    ↓
Classifier: qwen3 (local, free) classifies into tier
    ↓  (fails?)
Classifier: kimi (local, free) retries
    ↓  (fails?)
Classifier: deepseek-flash (~$0.0001) retries
    ↓  (fails?)
Classifier: cached tier from last success
    ↓
Hook injects routing decision into Claude's context
    ↓
Claude delegates to the right model or handles directly

9-Tier Routing Table

TierModelInput (per M)Output (per M)Handles
1Gemini 2.5 Flash-Lite$0.10$0.40Bulk extraction, classification, CIG pipelines
2DeepSeek V4 Flash$0.14$0.28Simple code, CRUD, test writing, small fixes
3DeepSeek V4 Pro$0.44$0.87Multi-file features, refactors, debugging (~80% of work)
4Gemini 2.5 Flash$0.15$0.60Multimodal (images, video, audio), brand analysis
5Kimi K2.6$0.60$2.50Code review, commit messages, diff summaries
6Gemini 3.1 Pro + Search$1.25$10.00Deep research, Google grounding, 2M context
7CodexvariesvariesBulk generation, code review
8Claude Sonnet/Opus$3-5$15-25Architecture, security, quality-critical

Delegation Commands

When the hook says "delegate to X", run the matching command and return its output:

# Tier 1 — Gemini Flash-Lite
~/bin/gemini --flash-lite "prompt"

# Tier 2 — DeepSeek Flash
~/bin/deepseek --flash "prompt"

# Tier 3 — DeepSeek Pro
~/bin/deepseek --pro "prompt"

# Tier 4 — Gemini Flash
~/bin/gemini --flash "prompt"

# Tier 5 — Kimi
~/bin/kimi --quiet -p "prompt"

# Tier 6 — Gemini Pro Search
~/bin/gemini --pro-search "prompt"

# Tier 7 — Codex
codex exec "prompt"

# Tier 8 — Claude
# Handle directly (no delegation)

Delegation Script Contract

Every ~/bin/ script follows the same pattern:

  1. Accepts prompt as argument: script "what is 2+2"
  2. Model flags: --flash, --pro, --flash-lite, --pro-search
  3. Quiet mode: --quiet (where applicable)
  4. Output: writes response to stdout, errors to stderr
  5. Exit codes: 0 on success, non-zero on failure

Available Scripts

~/bin/
├── qwen3       # Shell: curl to local Ollama API
├── kimi        # Shell: execs Kimi CLI binary
├── deepseek    # Python: httpx to DeepSeek Anthropic-compat API
├── gemini      # Python: httpx to Gemini OpenAI-compat API
├── research    # Python: multi-backend research with auto-evaluation
└── route-task  # Shell: qwen3-powered task classification

Classifier Fallback Chain

The classifier itself can fail. When it does, cascading fallback kicks in:

LevelClassifierCostThreshold
1qwen3 (Ollama)$02s connect, 8s classify
2kimi CLI$0Local process
3deepseek-flash~$0.0001API call
4Cached tier$0From ~/.claude/routing-cache.json

The cache (~/.claude/routing-cache.json) saves the last successful tier and timestamp. After compaction, when Ollama may be briefly unreachable, the cache ensures routing continues without dropping to CLAUDE by default.

Missing Wrapper Fallback

Before the hook emits a delegation instruction it checks that the tier's wrapper exists (the resolved flash/pro binary, ~/bin/gemini-api, ~/bin/gemini-cli, ~/bin/kimi, ~/bin/grok, or codex on PATH). If it is missing, the decision becomes ROUTING DECISION: CLAUDE (fallback from <tier>) and Claude handles the task directly, without the PLAN FIRST step. A cached tier the hook no longer knows is discarded the same way. There is no qwen3 delegation tier any more.

Tool Fallback Protocol

When Claude's built-in tools fail, external backends take over:

Failed ToolFallback 1Fallback 2
WebSearch / WebFetch~/bin/research "query"~/bin/deepseek --pro "query"
Read / file accesscat via Bash—
Grepgrep -r via Bash—

Research Tool (~/bin/research)

Multi-backend research with auto-evaluation:

  • Tries deepseek-flash → deepseek-pro in sequence
  • Scores results 0-10 on content quality, structure, length
  • Auto-adjusts preferred backend based on evaluation scores
  • View stats: ~/bin/research --eval
  • Score log: ~/.claude/research-eval.jsonl

Maggy Integration

Maggy's model_router.py mirrors the same 9-tier structure in DEFAULT_TIERS. The PiAdapter uses the same delegation scripts for execution. Task type overrides in routing_rules_defaults.py ensure:

  • research, competitor → Gemini Pro Search (Google grounding)
  • bulk → Gemini Flash-Lite (cheapest)
  • security, architecture, planning → Claude (quality-critical)
  • docs, tests → DeepSeek Pro (cost-efficient)
  • review → Claude (security + architecture depth)

Environment

# Required for delegation scripts (in ~/.zshrc)
export DEEPSEEK_API_KEY="sk-..."
export GEMINI_API_KEY="..."       # For gemini delegator
export OPENAI_API_KEY="sk-..."    # For codex CLI

# Ollama must be running locally for qwen3
ollama serve  # or launch at startup

Observability

  • Routing log: ~/.claude/routing-log.jsonl — every classification with tier, classifier used, tokens saved
  • Routing cache: ~/.claude/routing-cache.json — last tier for post-compact recovery
  • Research eval: ~/.claude/research-eval.jsonl — per-query backend scoring
  • Maggy routing heatmap: Dashboard → Models tab → per-model reward scores
Repository

alinaqi/maggy

Path

skills/model-routing/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.