# Have the agent judge overbuild instead of the human

Every proposed new job, hook or script must say what breaks without it.

By Ki Moon · 2026-10-26 · technique · current
Canonical: https://kihmoon.com/bench-notes/p/agent-judges-overbuild/

**Symptom:** Your list of scheduled jobs, hooks and scripts only grows, and several have no run or read in the last month.

Unneeded moving parts barely show in error data because an approver tends to accept them, leaving over-building at about 3% of classified errors. I can't reliably judge overkill mid-flow, and a written "default to lean" rule sat in memory for months without changing a recommendation.

So the check sits where approval happens.

A hook on the agent's question tool refuses any option that adds a moving part until it carries two lines, "Without it:" (what breaks, from evidence) and "Smallest:" (the lightest alternative, including doing nothing yet).

I picked that trigger by backtest. Scanning the agent's free text fired on 5.8% of replies, mostly checklists. The approval-call trigger hit about one question in ten.

It changes recommendations. In the latest weekly run it again fired on about one logged question in ten, and more than a third of those re-asks came back with a different recommendation.

Increments add up unnoticed, as in one afternoon when a calendar grew into a board, templates, an audit and a scoreboard.

## Check your setup (read-only)

List the jobs, hooks and scripts added in the last 90 days, from the job registry and hook config. Leave out jobs that run less often than monthly. Leave out alarms that only fire on failure. Look in run logs and session transcripts for a run or read of each in the last 30 days. Any item with neither is a retirement candidate.

**Passes if:** Every job, hook or script added in the last 90 days ran or was read in the last 30 days. The exclusions are jobs that run less often than monthly and alarms that only fire on failure.

**Access needed:** scheduler, local-config, agent-transcripts

## If it fails (changes to make later, not part of the check)

1. Refuse a proposal for a new job, hook, script, ticket, review pass or store until it states 2 things. The 2 things are what breaks without the addition and the smallest alternative.
2. Trigger the check on the approval call, not by scanning free text.
3. Defer each component to a named trigger, never a bare later.
4. Flag the growth after 3 increments to one system in a session, before a fourth increment.
5. Propose each month the removal of anything built 30 or more days ago that nothing uses. Exclude jobs that run less often than monthly and alarms that only fire on failure.

**Applies if:** Your work queue is the board, ticket list or file where agents file items for a person to act on. It, or your transcripts, show agents proposing new jobs, hooks or scripts that a person approves.

**Skip if:** No agent in your transcripts proposes new jobs, hooks or scripts. Or your approval log shows the approver rejecting agent proposals on scope in the last 90 days.

Tags: agents, approval, cost
