model-selection
Skill1 starsChanged 8 months agoMITView on GitHub
Model + thinking-effort orchestration. Reference when dispatching subagents (Agent tool or workflow agent() calls) and when setting session effort. Sonnet is the subagent floor; the main-loop model is the expensive decision-maker; effort is routed per task instead of maxed globally.
16 other projects use a version of this.
Adopted by
Most recently taken up by
- Walsworth-Group/physkittheir own version, first seen Nov 8, 2026
- github/squadtheir own version, first seen Nov 8, 2026
- agentstation/skillstheir own version, first seen Nov 1, 2026
- microsoft/github-vteam-industry-demostheir own version, first seen Oct 25, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- awslabs/agent-pluginstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use architectural-proposals, ci-validation-gates and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillarchitectural-proposals
How to write comprehensive architectural proposals that drive alignment before code is written
Also in 3 projects that use this
Microsoft AzureSkillci-validation-gates
Defensive CI/CD patterns: semver validation, token checks, retry logic, draft detection — earned from v0.8.22
Also in 3 projects that use this
- +10 more from Azure
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- github/gh-aw★ 5.6ksame name
- github/squad★ 3.4ksame name
- leookun/cursor-byok★ 3.2ksame name
- awslabs/agent-plugins★ 918same name
- Resgrid/Core★ 238same name
- nimadorostkar/Claude-Skills-collection★ 33same name
- Azure/apiops-cli★ 32same name
- han69611/math-modeling-skills★ 10same name
- yuanhao667/Skills★ 10same name
- tstapler/dotfiles★ 8same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository51 other files it gives its agents.
- algorithmic-artSkill
- audit-componentsSkill
- canvas-designSkill
- cascade-orchestrationSkill
- consultSkill
- data-reconciliationSkill
- debug-collaborateSkill
- deep-root-causeSkill
- deploy-allSkill
- design-reverse-engineerSkill
- design-showcaseSkill
- docxSkill
- env-auditSkill
- evolveSkill
- frontend-designSkill
- full-stack-buildSkill
- full-stack-traceSkill
- gh-repo-reconSkill
- grill-meSkill
- handoffSkill
- html-slidesSkill
- insightSkill
- internal-commsSkill
- isolation-testSkill
- mcp-builderSkill
- pdfSkill
- persistent-issueSkill
- pre-merge-reviewSkill
- premise-auditSkill
- propagate-featureSkill
- regression-bisectSkill
- research-gateSkill
- review-implSkill
- schema-checkSkill
- session-notesSkill
- skill-auditSkill
- skill-creatorSkill
- slack-gif-creatorSkill
- start-daySkill
- temporal-forensicsSkill
- theme-factorySkill
- throwaway-scriptSkill
- triage-ideasSkill
- verify-completeSkill
- webapp-testingSkill
- web-artifacts-builderSkill
- wisdomSkill
- worker-buildSkill
- worktree-guardSkill
- write-planSkill
- xlsxSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 22
The main-loop model is main-loop-only: Never dispatch subagents at the highest-tier model — Opus at max is the escalation ceiling for …
- Very specific: line 33
CLAUDE_CODE_SUBAGENT_MODEL: NEVER set this globally. It silently overrides every skill's per-agent model pins (flattening Opus reviewers … - Distinctive: line 43
Ask: "If this agent misses something, what happens?"
- Very specific: line 54
Opus effort preference (standing decision): when Opus depth is warranted beyond high, skip xhigh and go straight to max.
- Very specific: line 67
Every agent() call in a workflow script must pass model: explicitly — workflow agents otherwise inherit the main-loop model (the most …
- Distinctive: line 84
Don't mix models within one reviewer panel: If a review skill dispatches 5 reviewers, all 5 are Opus — inconsistent models make outputs …
- Very specific: line 85
Don't re-level the session for one hard question: Use ultrathink in that prompt.
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Model & Effort Orchestration
Goal: top-end reasoning only where the task warrants it. The main loop is the expensive decision-maker; everything it delegates should run on the cheapest model/effort that can't miss.
The stack — who runs what
| Layer | Model | Effort | Rationale |
| Main loop (orchestrator) | Your configured main-loop model (e.g. claude-fable-5[1m]) | session effortLevel: high | Adaptive thinking scales depth to the task at high; xhigh forces deep reasoning on every trivial turn. Escalate per session, not globally. |
| Standard subagents | sonnet | inherits session | Implementation, research, file reads, builds, deploys, report formatting. |
| Critical subagents | opus | high default, max for irreversible | Security review, adversarial analysis, architecture, financial logic, forensic RCA. |
| Pure code search | Explore subagent type | n/a | Harness-backed fast search agent — cheapest way to locate code. |
Floor rule: never dispatch below Sonnet for work that produces conclusions we act on. (Explore is the harness's own search agent and is exempt — it locates, it doesn't judge.)
The main-loop model is main-loop-only. Never dispatch subagents at the highest-tier model — Opus at max is the escalation ceiling for delegated work. If a problem genuinely needs main-loop-grade reasoning, it belongs in the main loop where the full session context lives.
Effort mechanics
The old note "effort is session-level only" is obsolete — per-agent effort now exists.
- Session:
/effort low|medium|high|xhigh|max(max is session-only). Persistent default:effortLevelin~/.claude/settings.json(allowed: low–xhigh). - Per-agent:
.claude/agents/*.mdfrontmatter supportseffort:alongsidemodel:— that agent runs at its own effort regardless of session level. - Per-prompt: include
ultrathinkin a prompt for a one-off deep pass without changing session state. - Precedence:
CLAUDE_CODE_EFFORT_LEVELenv > agent frontmatter > session/effort/effortLevelsetting. - Fable / Opus 4.8+: adaptive thinking only — it cannot be disabled; effort controls its depth. At
low/mediumthe model may skip thinking entirely on simple tasks.MAX_THINKING_TOKENSis deprecated for these models — do not use it. CLAUDE_CODE_SUBAGENT_MODEL: NEVER set this globally. It silently overrides every skill's per-agent model pins (flattening Opus reviewers to whatever it names). Routing lives in call sites, not env.
Session defaults (the system)
~/.claude/settings.json: setmodel:to your preferred main-loop model andeffortLevel: high—xhighforces max thinking on every turn, including trivial ones.- Escalate per session when the work is genuinely hard:
/effort xhighor/effort maxfor forensic debugging, schema-migration design, security-heavy merges. Drop to/effort mediumfor bulk-mechanical sessions (mass renames, data entry, doc sweeps). - Single hard question mid-session → say
ultrathinkin the prompt instead of re-leveling the session.
Routing matrix
Ask: "If this agent misses something, what happens?"
| Task class | Model | Effort | Dispatch |
| Mechanical: run builds/tests, curl endpoints, file moves, format reports | sonnet | medium | subagent_type: "routine" (pre-tiered) or Agent({ model: "sonnet" }) |
| Research, codebase mapping, doc reading | sonnet | session | Agent({ model: "sonnet" }); pure search → Explore |
| Implementation (worktree agents) | sonnet | session | Agent({ model: "sonnet", isolation: "worktree" }) |
| Critical review, security, architecture | opus | high | Agent({ model: "opus" }) |
| Irreversible decisions: migrations, prod RCA, merge gating, subtle multi-layer bugs | opus | max | subagent_type: "critical-reviewer" (pre-tiered opus+max) |
| Orchestration, synthesis of agent outputs, user-facing conclusions | main-loop model | session | don't delegate |
Opus effort preference (standing decision): when Opus depth is warranted beyond high, skip xhigh and go straight to max. Guessing the "between" tier adds decision overhead without reliably saving cost. high when it suffices; max when it doesn't.
Pre-tiered agents (.claude/agents/)
| Agent | Model | Effort | Use for |
routine | sonnet | medium | Mechanical chores where the output is verifiable (exit codes, HTTP statuses, diffs). Add isolation: "worktree" if it modifies code. |
critical-reviewer | opus | max | Adversarial review of irreversible changes — the effort pin means it gets max thinking even when the session runs at high. |
Dispatch via Agent({ subagent_type: "routine", ... }). These exist so the effort pin travels with the agent definition instead of depending on session state.
Workflows
Every agent() call in a workflow script must pass model: explicitly — workflow agents otherwise inherit the main-loop model (the most expensive possible default). Pattern: sonnet for runners/probes/judges, opus for synthesis/verdicts.
Skills that dispatch agents
| Skill | Recommended model |
/start-day, /session-notes, /audit-components, /merge-to-main checks | sonnet (mechanical/research) |
/review-impl, /pre-merge-review, security audits | opus (reviewers) |
/worker-build, /full-stack-build | scaffold/implement = sonnet, review = opus |
/qa-sweep view judges | sonnet |
Forensic teams (/deep-root-cause, /temporal-forensics, etc.) | opus, consider critical-reviewer for the verdict agent |
What NOT to do
- Don't dispatch unpinned. An unpinned file-search agent inherits the main-loop model and burns its tokens at session effort for zero quality gain. Every
Agent()/agent()call states its model. - Don't use Haiku for judgement work. The floor is Sonnet. (Explore's internal model is the harness's business.)
- Don't set
CLAUDE_CODE_SUBAGENT_MODELorCLAUDE_CODE_EFFORT_LEVELenv vars. They override all per-call and per-agent routing silently. - Don't mix models within one reviewer panel. If a review skill dispatches 5 reviewers, all 5 are Opus — inconsistent models make outputs incomparable.
- Don't re-level the session for one hard question. Use
ultrathinkin that prompt.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

