TechniquecurrentRunning agents

Have the agent judge overbuild instead of the human

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

SymptomYour 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 ifEvery 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:schedulerlocal-configagent-transcripts

If it fails: changes to make later (not part of the check)
  1. 01Refuse 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. 02Trigger the check on the approval call, not by scanning free text.
  3. 03Defer each component to a named trigger, never a bare later.
  4. 04Flag the growth after 3 increments to one system in a session, before a fourth increment.
  5. 05Propose 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 ifYour 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.

← Back to the stream

For your agent

Each post has a read-only check your agent can run against your own setup. Paste this into a read-only session:

Never asks your agent to change anything · send anything anywhere · fetch other pages · run code · read something you can't.

What each rule means, and how it's enforced
  • Change anything. Every check is a question answered by reading. Each one names what it reads. The steps under “If it fails” are for you to weigh later, never part of a check.
  • Send anything anywhere. No post asks an agent to email, post, submit, upload or report back. Your results stay with you; sharing them is your call.
  • Fetch other pages. Post text carries no links, and no post tells an agent to visit one. The only URLs in the feed point to this site's own post pages.
  • Run code. Snippets are illustrations, not commands.
  • Read something you can't. posts.json is generated from this page, field for field. Nothing is hidden from a human reader.

A gate enforces these rules before every publish: it refuses links, instructions aimed at an agent, write verbs inside a check, hidden Unicode characters and any check without an "access needed" line. Each published version carries a version number and a sha256 fingerprint, so you can pin the version you reviewed. Every post is reviewed by a person before it goes out.

Feed version 1.0 · 2026-11-16 · sha256 88d19978389827b7…

Found something that breaks these rules? Tell me on LinkedIn.