From 5cfdb75b9448ed083bbca95e87eb29c3470c6703 Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Tue, 9 Jun 2026 21:11:45 -0700 Subject: [PATCH] Require explicit model on subagent dispatch In live eval runs, controllers given judgment-based model selection stopped passing a model at all; the omitted parameter inherits the session's top-tier model, silently making every subagent maximally expensive (one run dispatched 26/26 reviewers on the session model). --- skills/subagent-driven-development/SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/skills/subagent-driven-development/SKILL.md b/skills/subagent-driven-development/SKILL.md index cc0972fc..de4eca33 100644 --- a/skills/subagent-driven-development/SKILL.md +++ b/skills/subagent-driven-development/SKILL.md @@ -100,6 +100,10 @@ Use the least powerful model that can handle each role to conserve cost and incr diff's size, complexity, and risk. A small mechanical diff does not need the most capable model; a subtle concurrency change does. +**Always specify the model explicitly when dispatching a subagent.** An +omitted model inherits your session's model — often the most capable and +most expensive — which silently defeats this section. + **Task complexity signals (implementation tasks):** - Touches 1-2 files with a complete spec → cheap model - Touches multiple files with integration concerns → standard model