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

Waste found after a job runs is found too late.

By Ki Moon · 2026-05-12 · technique · current
Canonical: https://kihmoon.com/bench-notes/p/lint-agents-for-token-waste/

**Symptom:** A 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 if:** Every 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:** scheduler, local-config

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

1. Review each skill, scheduled routine, dispatch template or model-calling script against a token-waste checklist before it counts as done.
2. Report only the checklist items that trip, each with a concrete fix. Give the rest as one count.
3. Keep stable reference data in a file and script edits from it instead of re-emitting it through the model.
4. Add 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 if:** Your skills folder or scheduler holds a skill or job that calls a model more than once per run.

**Skip if:** No scheduled job or skill in your setup calls a model, and your model use is sessions you watch.

Tags: cost, agents
