TechniquecurrentRunning agents

Review an agent job's token cost before its first run

Waste found after a job runs is found too late.

SymptomA usage-limit refusal stops a job, and nobody can say which earlier job spent the budget.

My scheduled routines and skills share one token budget with the work I do by day. When a usage budget runs short, asking jobs what they spent after they ran finds the waste too late.

A token budget is shared capacity. A token spent on waste is a job that doesn't run.

Once a job has burned the budget, finding the waste is a postmortem.

So anything that calls a model repeatedly gets a token-waste review before it counts as done. Three pieces hold it together:

  • A review skill is the lint.
  • One line in my project instructions makes it a gate.
  • The end-of-session review adds each new pattern it sees.

The checklist started with 15 patterns and now holds 191, each with the case that produced it and a fix. The review reports only the items that trip, plus a count of the rest.

One typical entry is a 7 KB config body re-emitted through model output on four one-field updates for about 28 KB of output. Keeping that data on disk and scripting each update from the file keeps it out of the model.

Check your setup read-only

Read the job registry and the skills folder. List the skills and scheduled jobs that call a model more than once per run. Look for a dated cost review of each one before its first run. Any such job without a review is a gap.

Passes ifEvery skill or scheduled job that calls a model more than once per run has a cost review. Each review is dated before the job's first run.

Access needed:schedulerlocal-config

If it fails: changes to make later (not part of the check)
  1. 01Review each skill, scheduled routine, dispatch template or model-calling script against a token-waste checklist before it counts as done.
  2. 02Report only the checklist items that trip, each with a concrete fix. Give the rest as one count.
  3. 03Keep stable reference data in a file and script edits from it instead of re-emitting it through the model.
  4. 04Add each new waste pattern to the checklist, with its case and fix. Make the addition at the end of the session that found the pattern.
Applies ifYour skills folder or scheduler holds a skill or job that calls a model more than once per run.

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