model-tier-rightsizing

Routes agent dispatches to certified model tiers by wrong-output blast radius and verification strength.

Updated Jun 30, 2026
One-click install
npx skills add https://github.com/Codeseys-Labs/agentic-sdlc --skill model-tier-rightsizing-codeseys-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: model-tier-rightsizing
Source: https://github.com/Codeseys-Labs/agentic-sdlc/tree/main/plugin/skills/model-tier-rightsizing
Command: npx skills add https://github.com/Codeseys-Labs/agentic-sdlc --skill model-tier-rightsizing-codeseys-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Agent workflows often pick models by prestige or habit, wasting budget on trivial tasks or risking silent failures on high-stakes ones. This Skill enforces a dispatch contract that matches each task to a model tier based on the consequence of a wrong answer, and blocks any dispatch lacking certified model identity, effort, and context evidence. ## Core Features & Use Cases - Four-tier dispatch ladder: Routes work across frontier/derail, judgment workhorse, capable volume, and mechanical floor tiers using certified exact model IDs and effort bands. - RuntimeAssignment receipt validation: The receipt_admission.py script validates dispatch receipts against a versioned policy, rejecting prompt echoes, unverified aliases, and request-derived readback masquerading as transport evidence. - Route qualification gating: route_qualification.py issues, validates, admits, and quarantines route/task-class qualification cells with 30-day expiry, so conductors can check dispatchability before writing an assignment. - Local qualification and Pareto evidence: rightsize.py measures routes against digest-bound task packs with Wilson lower-bound thresholds and computes per-task-class Pareto fronts. - Use Case: Before dispatching a semantic code review worker, run the admission check to confirm the exact model/effort/context tuple is qualified and admitted; if refused, return one advisory SeedProposal instead of dispatching. ## Quick Start Ask the agent to load the canonical calibration reference and classify your task's blast radius before writing any RuntimeAssignment that names a model or effort.

Frequently Asked Questions about model-tier-rightsizing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose which model tier to dispatch a task to?

Classify the task by wrong-output blast radius: settled-truth work goes to the frontier pair, silent-degradation risk to the judgment workhorse pair, deterministically gated work to capable volume, and fully checked redo to the mechanical floor. Importance alone never moves a task up a tier.

How do I validate a RuntimeAssignment receipt before dispatch?

Pipe the receipt JSON into scripts/receipt_admission.py, which checks it against the versioned runtime-assignment-receipt-v1 policy. It rejects duplicate members, prompt echoes, caller defaults, and request-derived bytes masquerading as transport readback, emitting a deterministic validated or invalid verdict.

What is the difference between route qualification and receipt validation?

Route qualification (route_qualification.py) answers whether an exact route and task-class cell currently holds a qualified generation, with 30-day expiry and quarantine support. Receipt validation checks one concrete assignment's internal schema and digest consistency; neither implies the other.

Can benchmark results like DeepSWE or CursorBench qualify a model route?

No. Mined benchmark evidence can only nominate and order candidates for local evaluation. Qualification requires a target-representative task pack with at least five held-out tasks, three attempts each, 90% acceptance, and a 95% Wilson lower bound of 0.70.

Why does dispatch stop when model identity readback is unavailable?

A requested value, host default, or alias is not resolution evidence. The contract requires resolution_state resolved with independent provider and model observation, or an unambiguous policy mapping; unresolved or unverified identity fails closed before dispatch.

Does the skill dispatch or spawn workers itself?

No. It supplies evaluation and validation surfaces only. An external authenticated harness remains the sole production admission and spawn authority, invoking validation immediately before spawn and correlating digests with immutable spawn evidence.