feat(agents): pin the four inherit toolkit reviewers to opus (−10.6% pr-reviewer spend)

modules/agents/subagents/README.md

@@ -10,4 +10,9 @@ This `subagents/` dir is symlinked to `~/.claude/agents/` (see `symlinks.conf`),
 the location Claude Code scans for subagents. It is named `subagents/` here for
 clarity; identity comes from each file's `name:` frontmatter, not the path.
 
-Re-sync: copy the updated `*.md` files from the plugin's `agents/` dir.
+Re-sync: copy the updated `*.md` files from the plugin's `agents/` dir, then
+re-apply the local modification below — a plain copy silently reverts it.
+
+Local modification: every agent pins `model: opus` in its frontmatter (a
+deliberate cost decision — see PR #139 and DJRHails/gantry#942); upstream
+ships some of them as `model: inherit`.

modules/agents/subagents/comment-analyzer.md

@@ -1,7 +1,7 @@
 ---
 name: comment-analyzer
 description: Use this agent when you need to analyze code comments for accuracy, completeness, and long-term maintainability. This includes (1) after generating large documentation comments or docstrings, (2) before finalizing a pull request that adds or modifies comments, (3) when reviewing existing comments for potential technical debt or comment rot, and (4) when you need to verify that comments accurately reflect the code they describe. See "When to invoke" in the agent body for worked scenarios.
-model: inherit
+model: opus
 color: green
 ---
 

modules/agents/subagents/pr-test-analyzer.md

@@ -1,7 +1,7 @@
 ---
 name: pr-test-analyzer
 description: Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Typical triggers include the user asking whether tests on a freshly-created PR are thorough, an updated PR adding new logic that needs coverage analysis, and a final pre-merge double-check before marking a PR ready. See "When to invoke" in the agent body for worked scenarios.
-model: inherit
+model: opus
 color: cyan
 ---
 

modules/agents/subagents/silent-failure-hunter.md

@@ -1,7 +1,7 @@
 ---
 name: silent-failure-hunter
 description: Use this agent when reviewing code changes in a pull request to identify silent failures, inadequate error handling, and inappropriate fallback behavior. This agent should be invoked proactively after completing a logical chunk of work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors. Examples:\n\n<example>\nContext: Daisy has just finished implementing a new feature that fetches data from an API with fallback behavior.\nDaisy: "I've added error handling to the API client. Can you review it?"\nAssistant: "Let me use the silent-failure-hunter agent to thoroughly examine the error handling in your changes."\n<Task tool invocation to launch silent-failure-hunter agent>\n</example>\n\n<example>\nContext: Daisy has created a PR with changes that include try-catch blocks.\nDaisy: "Please review PR #1234"\nAssistant: "I'll use the silent-failure-hunter agent to check for any silent failures or inadequate error handling in this PR."\n<Task tool invocation to launch silent-failure-hunter agent>\n</example>\n\n<example>\nContext: Daisy has just refactored error handling code.\nDaisy: "I've updated the error handling in the authentication module"\nAssistant: "Let me proactively use the silent-failure-hunter agent to ensure the error handling changes don't introduce silent failures."\n<Task tool invocation to launch silent-failure-hunter agent>\n</example>
-model: inherit
+model: opus
 color: yellow
 ---
 

modules/agents/subagents/type-design-analyzer.md

@@ -1,7 +1,7 @@
 ---
 name: type-design-analyzer
 description: Use this agent when you need expert analysis of type design in your codebase. Specifically use it (1) when introducing a new type to ensure it follows best practices for encapsulation and invariant expression, (2) during pull request creation to review all types being added, and (3) when refactoring existing types to improve their design quality. The agent will provide both qualitative feedback and quantitative ratings on encapsulation, invariant expression, usefulness, and enforcement. See "When to invoke" in the agent body for worked scenarios.
-model: inherit
+model: opus
 color: pink
 ---