agentleFS
aemerson-commitsaemerson-commits/shareable-skills/skills/model-selection/SKILL.md

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

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 AzureSkill

    architectural-proposals

    How to write comprehensive architectural proposals that drive alignment before code is written

    Also in 3 projects that use this

  • Microsoft AzureSkill

    ci-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

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
  1. Very specific:

    The main-loop model is main-loop-only: Never dispatch subagents at the highest-tier model — Opus at max is the escalation ceiling for …

    line 22
  2. Very specific:

    CLAUDE_CODE_SUBAGENT_MODEL: NEVER set this globally. It silently overrides every skill's per-agent model pins (flattening Opus reviewers …

    line 33
  3. Distinctive:

    Ask: "If this agent misses something, what happens?"

    line 43
  4. Very specific:

    Opus effort preference (standing decision): when Opus depth is warranted beyond high, skip xhigh and go straight to max.

    line 54
  5. Very specific:

    Every agent() call in a workflow script must pass model: explicitly — workflow agents otherwise inherit the main-loop model (the most …

    line 67
  6. Distinctive:

    Don't mix models within one reviewer panel: If a review skill dispatches 5 reviewers, all 5 are Opus — inconsistent models make outputs …

    line 84
  7. Very specific:

    Don't re-level the session for one hard question: Use ultrathink in that prompt.

    line 85

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

LayerModelEffortRationale
Main loop (orchestrator)Your configured main-loop model (e.g. claude-fable-5[1m])session effortLevel: highAdaptive thinking scales depth to the task at high; xhigh forces deep reasoning on every trivial turn. Escalate per session, not globally.
Standard subagentssonnetinherits sessionImplementation, research, file reads, builds, deploys, report formatting.
Critical subagentsopushigh default, max for irreversibleSecurity review, adversarial analysis, architecture, financial logic, forensic RCA.
Pure code searchExplore subagent typen/aHarness-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: effortLevel in ~/.claude/settings.json (allowed: low–xhigh).
  • Per-agent: .claude/agents/*.md frontmatter supports effort: alongside model: — that agent runs at its own effort regardless of session level.
  • Per-prompt: include ultrathink in a prompt for a one-off deep pass without changing session state.
  • Precedence: CLAUDE_CODE_EFFORT_LEVEL env > agent frontmatter > session /effort / effortLevel setting.
  • Fable / Opus 4.8+: adaptive thinking only — it cannot be disabled; effort controls its depth. At low/medium the model may skip thinking entirely on simple tasks. MAX_THINKING_TOKENS is 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: set model: to your preferred main-loop model and effortLevel: high — xhigh forces max thinking on every turn, including trivial ones.
  • Escalate per session when the work is genuinely hard: /effort xhigh or /effort max for forensic debugging, schema-migration design, security-heavy merges. Drop to /effort medium for bulk-mechanical sessions (mass renames, data entry, doc sweeps).
  • Single hard question mid-session → say ultrathink in the prompt instead of re-leveling the session.

Routing matrix

Ask: "If this agent misses something, what happens?"

Task classModelEffortDispatch
Mechanical: run builds/tests, curl endpoints, file moves, format reportssonnetmediumsubagent_type: "routine" (pre-tiered) or Agent({ model: "sonnet" })
Research, codebase mapping, doc readingsonnetsessionAgent({ model: "sonnet" }); pure search → Explore
Implementation (worktree agents)sonnetsessionAgent({ model: "sonnet", isolation: "worktree" })
Critical review, security, architectureopushighAgent({ model: "opus" })
Irreversible decisions: migrations, prod RCA, merge gating, subtle multi-layer bugsopusmaxsubagent_type: "critical-reviewer" (pre-tiered opus+max)
Orchestration, synthesis of agent outputs, user-facing conclusionsmain-loop modelsessiondon'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/)

AgentModelEffortUse for
routinesonnetmediumMechanical chores where the output is verifiable (exit codes, HTTP statuses, diffs). Add isolation: "worktree" if it modifies code.
critical-revieweropusmaxAdversarial 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

SkillRecommended model
/start-day, /session-notes, /audit-components, /merge-to-main checkssonnet (mechanical/research)
/review-impl, /pre-merge-review, security auditsopus (reviewers)
/worker-build, /full-stack-buildscaffold/implement = sonnet, review = opus
/qa-sweep view judgessonnet
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_MODEL or CLAUDE_CODE_EFFORT_LEVEL env 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 ultrathink in that prompt.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.