TechniquecurrentRunning agents

A cost fix that cuts coverage changes what the job does

I split token fixes by what they can break instead of what they save.

SymptomA job's token use dropped after an efficiency pass, and its output count dropped with it.

My token-waste review proposes fixes. At first every fix waited for my approval, and approving every fix trains me to stamp them. Skipping approval lets an efficiency change quietly change what a job does.

On one review, 2 of the 8 proposed fixes looked like savings and were really changes to what the job covered.

In a second case, a rewrite of a nightly enrichment job used about a fifteenth of the old version's tokens on one run.

It also found about a third fewer people than the old version, and that count, not the token count, decides whether such a rewrite ships.

The lost people sat on older email threads that had been re-ingested. Their activity dates fell outside the window the cheaper query filtered on. The job feeds the CRM, so the saving meant fewer records reached it.

So fixes now split by blast radius, and the split decides whether I look before a fix lands.

For auto-applied fixes, a clean record on work written minutes earlier is the easy case. It says little about older work, or someone else's. When an auto-applied fix turns out wrong, shrink the auto-apply list rather than going back to asking on everything.

Check your setup read-only

List the jobs whose git log shows a cost cut in the last 90 days. Read each job's run log. Compare its output and input counts for the week before and the week after the cut. Any output drop the inputs don't explain means the cut reduced coverage, and that's a gap.

Passes ifOutput counts after the cut move with input counts, inside the job's usual week-to-week range.

Access needed:schedulerlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Apply behaviour-preserving fixes without asking. Behaviour-preserving fixes include deduplicated prompt text, prompt caching, and a pointer instead of a restated doc. Output bounds that don't truncate results are also behaviour-preserving.
  2. 02Ask before any fix that changes coverage. Coverage fixes include kill criteria, abort thresholds and dropped inputs. Coverage fixes also include a collapsed or serialized fan-out and batching units into fewer agents.
  3. 03Ask before downgrading the model on a stage that needs judgment.
  4. 04Compare output counts before and after every cost fix, not only tokens.
  5. 05Report every applied fix with its checklist number, even when nothing needed approval.
Applies ifYour git log shows a cost cut to a job that writes CRM records or feeds a list.

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