athola/claude-night-market/agent-expenditure

Claude Code and agent skill by athola/claude-night-market

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Tracks per-agent token usage and flags waste in parallel dispatch. Use when evaluating parallel agent efficiency or after a multi-agent run.

Install

npx vskill@latest install athola/claude-night-market/agent-expenditure

SKILL.md

Agent Token Waste Monitoring

When To Use

  • After parallel agent dispatch completes
  • When evaluating whether to increase agent count
  • During retrospectives on agent-heavy workflows
  • When plan-before-large-dispatch rule triggers

When NOT To Use

  • Single-agent workflows (no coordination overhead)
  • During active agent execution (post-hoc analysis)
  • For token budgeting (use token-conservation instead)

Brooks's Law for Agents

Dispatching more agents does not always help. Coordination overhead grows with agent count:

Agent CountExpected OverheadGuidance
1-3NegligibleDispatch freely
4-510-15%Acceptable; plan first
6-820-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.

Post-Dispatch Review Checklist

After parallel agent runs, evaluate:

  1. Did each agent produce unique findings?
  2. Was total token expenditure proportional to value?
  3. Did any agent duplicate another's work?
  4. Would fewer agents have produced the same result?

If 2+ questions answer no, reduce agent count in future dispatches of the same type.

Waste Signals

See modules/waste-signals.md for the 5 waste signal categories and detection criteria.

Cross-References

  • Dispatching 4 or more agents needs an agreed plan first: the

roster, each agent's scope, and the output contract it returns. 1-3 agents may dispatch directly.

  • conserve:token-conservation for session-level token budgeting
  • conjure:agent-teams for dispatch coordination

Exit Criteria

  • [ ] All 4 post-dispatch review questions answered with explicit

yes/no per agent (unique findings, proportional expenditure, no duplication, fewer agents sufficient)

  • [ ] Waste signals from modules/waste-signals.md checked against

the completed run; any triggered signal named with the category

  • [ ] A recommendation is produced: either "reduce agent count to N"

or "dispatch was efficient" with coordination overhead percentage

  • [ ] If 2+ review questions answer no, a concrete agent-count

reduction is stated for future dispatches of the same type

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
342
Repository forks
37
7-day trend score
29

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/athola/claude-night-market/agent-expenditure/badge)](https://verified-skill.com/skills/athola/claude-night-market/agent-expenditure)

Something wrong with this skill or its page? Tell us.