What problem does it solve? Choosing the right model tier for each engineering task is hard to keep consistent across Claude Code, Codex, and AFK execution, and copying tier tables into executor prompts causes the classification criteria to drift. This Skill centralizes the RedSkills dev model tier policy so every task runs on the cheapest capable tier and escalates on evidence. ## Core Features & Use Cases - Tier classification policy: Defines the validate, simple, complex, and think tiers with default Claude, Codex, and MiniMax model/effort values and concrete classification criteria. - Deterministic-first validation: Directs structural checks (schema, lint, tests, type checks) to run before spending any model tokens on fuzzy validation. - Escalation and runtime overrides: Documents evidence-based escalation between tiers and the --model/RED_AFK_MODEL override precedence for ad-hoc and CI runs. - Use Case: When triaging an issue for autonomous execution, consult this policy to decide whether it is a simple single-scope change or a complex cross-module change, then let AFK route the tier to the right model. ## Quick Start Ask the agent to classify an issue using the model tier policy and explain which tier should execute it and why.