Route agent work across cheap, mid, and max models with SKILL.md

Write SKILL.md that tells agents (and humans driving them) which model tier to use for which task. Goal: lower cost on shallow work without using a max model for grep-and-summarize or a cheap model for risky refactors.

Team context:
[products: Cursor, Claude Code — which you use]
[your tier names: e.g. fast / default / max — map to actual model picks in your org]
[repo type: app, infra, monorepo — affects test commands]
[merge gates: required CI jobs, human review rules]

SKILL.md must include:
1. Purpose — predictable spend and quality: right model for the step, explicit escalation when stuck.
2. When to use — start of any multi-step agent session on this repo. When not to use — single one-line typo fix where tier is obvious.
3. Tier definitions (agent fills with your names, not vendor marketing):
   - Fast tier: read files, explain code, draft comments, run read-only git/log, small doc edits, enumerate options — no multi-file refactors.
   - Mid tier: implement bounded features, fix failing unit tests, update types across ≤ N files [set N e.g. 5], routine dependency bumps with skill-assisted review.
   - Max tier: cross-cutting refactors, security-sensitive changes, migration/rollback design, novel architecture, debugging after two failed mid-tier attempts on same task.
4. Routing table the agent must follow (markdown table):
   - Task pattern → default tier → escalate when
   - Examples: "summarize PR diff" → fast; "implement ticket with tests" → mid; "redesign auth flow" → max.
5. Escalation protocol:
   - Document what was tried at lower tier (commands run, files touched).
   - Human may override down only with written acceptance of risk in PR.
   - Never downgrade tier to save tokens on tasks marked Block/Warn in other skills (security, migrations).
6. Session habits:
   - Open with tier declaration in agent notes: "Tier: fast — scope: read billing module."
   - Re-evaluate tier after each milestone, not only at start.
   - Stop and ask human before max tier if estimate exceeds [budget note or timebox].
7. Cost hygiene without cheating:
   - Prefer targeted file reads over whole-repo uploads.
   - Batch test runs; do not re-run full e2e on every typo at max tier.
8. Two example prompts: "explain this module" (fast) vs "refactor payment service with characterization tests" (mid → max if tests red twice).
9. Pitfalls: max tier for exploration, fast tier for SQL migrations, switching models mid-diff without re-reading constraints, hiding failed attempts when escalating.
10. Done means: tier stated at session start, task completed at declared tier or escalation documented, no security/migration work at fast tier.

Rules:
- Map tiers to models your team actually pays for; use [confirm model name] placeholders if policy is unset.
- Do not claim exact dollar savings — describe relative cost only.
- Output only SKILL.md markdown.