athola/agent-expenditure
Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.
npx skills add https://github.com/athola/claude-night-market --skill agent-expenditure
Dispatching more agents does not always help. Coordination overhead
grows with agent count:
| Agent Count | Expected Overhead | Guidance |
|-------------|-------------------|----------|
| 1-3 | Negligible | Dispatch freely |
| 4-5 | 10-15% | Acceptable; plan first |
| 6-8 | 20-30% | Monitor closely |
| 9+ | 30%+ | Likely counterproductive |
Coordination overhead is measured as shared-file conflicts: concurrent
Read/Write operations on the same file by different agents, as a
percentage of total agent runtime.
After parallel agent runs, evaluate:
If 2+ questions answer no, reduce agent count in future dispatches
of the same type.
See modules/waste-signals.md for the 5 waste signal categories and
detection criteria.
.claude/rules/plan-before-large-dispatch.md for the 4+ agentplanning requirement
conserve:token-conservation for session-level token budgetingconjure:agent-teams for dispatch coordinationyes/no per agent (unique findings, proportional expenditure, no
duplication, fewer agents sufficient)
modules/waste-signals.md checked againstthe completed run; any triggered signal named with the category
or "dispatch was efficient" with coordination overhead percentage
reduction is stated for future dispatches of the same type
Take athola/agent-expenditure from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.