FindingcurrentRunning agents

A sub-agent has a fixed token cost, so small work is cheaper inline

In my setup each sub-agent paid 70 to 85k tokens before it did any work.

SymptomA fan-out of one sub-agent per small task costs far more tokens than the tasks' tool calls explain.

Each sub-agent starts by loading its base instructions, tool schemas and orientation. I measured that at about 70 to 85k tokens per agent, whatever the task size.

I had been dispatching one agent per file to republish pages, about two tool calls of real work each.

Batching 5 to 9 files per agent took a round from about 600 to 900k tokens to about 160 to 255k. Reliability held, because the return contract kept one result line per file.

If the repeat is deterministic, like a regex-safe edit across files, it shouldn't be an agent at all.

Resuming a finished agent is cheaper still, because it keeps its warm context and costs no new spawn.

That breaks down when files on disk have changed since the agent read them.

A drafter I resumed through two rounds of template and voice edits held the old versions in context and blended them with the new. Its output looked compliant while missing the edits, so the final run went to a fresh agent.

That resume-or-respawn call depends on knowing which files an agent read, so that list needs a record outside the orchestrator's head.

Check your setup read-only

Take the most recent session that spawned 5 or more sub-agents for the same kind of task. List each sub-agent's total tokens beside the tool calls it made on the task itself. Any sub-agent with tens of thousands of tokens on 2 or 3 task calls should have been batched or scripted.

Passes ifNo sub-agent in the sampled session spent tens of thousands of tokens on 2 or 3 task calls.

Access needed:agent-transcripts

If it fails: changes to make later (not part of the check)
  1. 01Batch mechanical repeats 5 to 10 per agent, with one result line per unit in the return contract.
  2. 02Script any repeat that is deterministic instead of dispatching an agent.
  3. 03Resume a finished agent when the inputs are new and the files it read are unchanged.
  4. 04Respawn a fresh agent once its contract files changed. Name the changed files for re-reading in the resume message when only 1 or 2 changed.
Applies ifYour transcripts show sessions that spawn several sub-agents for small repeated tasks, or reuse one agent across rounds.

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