← ClaudeAtlas

loadout-routerlisted

Choose the right model tier and agent for a coding task, and hand work off between Claude Code and Codex. Use when the user asks which model to use, mentions running low on usage or quota, wants to save tokens or cost, asks whether to switch to Opus/Sonnet/Haiku or a GPT tier, or wants to delegate a task to another agent.
VirajMishra1/loadout · ★ 4 · AI & Automation · score 77
Install: claude install-skill VirajMishra1/loadout
# Loadout Router Route each coding task to the cheapest model that still does it well, and hand work between agents when a different one is better suited. This skill wraps the `loadout` CLI, so the model catalog and pricing stay current with the installed version rather than going stale in this file. ## Prerequisite Check once per session: ```bash loadout --version ``` If that fails, tell the user to install it (`npm install --global loadout-ai`) and answer from general knowledge instead of guessing at specifics. ## Choosing a model Run the router with the task described in plain words: ```bash loadout route <task description> ``` It classifies the task into one of six phases — plan, implement, review, test, debug, document — and prints the recommended tier, the models in that tier with current prices, which of the user's installed agents can run them, and a cheaper fallback with its tradeoff. Report the recommendation and the reason. Name the actual model, not just the tier. If the output lists a `Conserve:` alternative, mention it only when the user cares about cost or quota, otherwise it is noise. When the user is explicit about the phase, skip classification: ```bash loadout route --phase review ``` ## When the user is low on usage If the user mentions running out, being rate limited, conserving quota, or stretching a plan, add `--conserve`: ```bash loadout route --conserve <task description> ``` This drops each phase one tier and prints the tradeoff you