model-routerlisted

# Model Router Turn a task into an explainable, executable provider plan. This skill advises; it does not authorize or invoke paid provider work. ## Procedure 1. State the task goal and concrete deliverables. 2. Decompose compound requests into model-sized steps. Keep steps separate when they have different modalities, privacy boundaries, or validation methods. 3. Capture hard constraints: modality, quality, latency, privacy, region, license, budget, local-versus-hosted preference, and required output format. 4. Query all relevant live provider tools. Use the exact provider contract in [provider-contract.md](references/provider-contract.md). 5. Eliminate candidates that violate a hard constraint. Do not rank an infeasible candidate above a feasible one because its quality looks better. 6. Compare the feasible set. Separate observed evidence from provider claims and unknowns. 7. Select a primary model and ordered fallbacks. A recommendation may remain a Pareto set when quality, cost, privacy, and latency cannot be reduced to one honest score. 8. If the selected provider/model requires a credential, add a plain-language `Secret setup` section naming the provider-native login or exact host environment variable. Do not ask for the value before model selection, and do not write or echo it. 9. Emit a JSON plan conforming to [model-task-plan.schema.json](references/model-task-plan.schema.json). 10. Set `consent.status` to `pending` whenever any st