En

agent-expenditure

Track multi-agent token consumption and identify waste in parallel scheduling

效率工具 分析Token消耗监控资源消耗控制费用支出核算AI调用成本 claude ★ 1.1k Updated 2026-08-02

Install & Use

Copy this prompt and send it to your AI assistant (Claude / Cursor / TRAE / Codex / WorkBuddy etc.) to auto-install:

Help me install this AI Skill: agent-expenditure.
It is used for: Track multi-agent token consumption and identify waste in parallel scheduling
Full Skill content: https://321skill.com/skills/agent-expenditure-x-2/raw/index.md
Read that page and install it.

The prompt includes a link to the full Skill content. You can also view the full content.

This Skill addresses the challenge of quantifying token waste in multi-agent parallel scheduling. In real-world development, when multiple AI agents are dispatched simultaneously to perform tasks, coordination overhead and redundant work can cause token consumption to spike, yet developers often rely on intuition to judge whether usage is excessive. This tool tracks each agent's token usage, calculates the coordination overhead ratio based on Brooks' Law, and automatically flags waste signals.

Usage is straightforward: after parallel agent scheduling is complete, simply trigger the analysis via a natural language command. It automatically reads the agent run logs, tallies each agent's token consumption and shared file conflict counts, and generates a coordination overhead report. You can then adjust subsequent scheduling strategies based on the report's recommendations (e.g., reducing the number of agents, optimizing task decomposition).

It is particularly well-suited for teams or individuals who frequently engage in multi-agent collaboration, especially those already experiencing token budget overruns or issues with duplicate agent outputs. For developers and operations engineers managing multiple parallel agent tasks, this tool provides data-driven decision-making support, helping to avoid blindly increasing the agent count.

It is recommended to use this tool for retrospective analysis after each large-scale parallel scheduling session. Note that it is primarily designed for post-hoc analysis and cannot intervene in real-time during agent execution. Additionally, ensure that agent logs include token consumption and file operation records. For single-agent workflows, this tool will not produce meaningful data.

Key Features

Unlike token-conservation tools, it focuses on analyzing waste after parallel scheduling rather than session-level budget control. It also introduces Brooks' Law to quantify coordination overhead, going beyond simply tallying total token counts.

Limitations

Requires a Claude Code environment and agent logs containing token consumption and file operation records. Only supports post-hoc analysis and cannot intervene in real-time.

FAQ

How do I install this Skill?

Run `claw install agent-expenditure` in Claude Code to install it.

Which AI platforms are supported?

Currently, it only supports the Claude Code environment and requires agents to use a shared file system.

Installation guide for AI assistants

If your AI coding assistant (Claude Code, Cursor, TRAE etc.) can see this page, send it this message to auto-install:

Visit https://321skill.com/skills/agent-expenditure-x-2/raw/index.md to read the original Skill definition (Markdown format) for agent-expenditure, and install it according to the instructions.