agent-expenditure

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Agent Token Waste Monitoring

Agent Token浪费监控

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

并行Agent调度完成后
评估是否增加Agent数量时
在以Agent为主的工作流回顾期间
触发“大规模调度前规划”规则时

When NOT To Use

不适用场景

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

单Agent工作流（无协调开销）
Agent执行过程中（仅支持事后分析）
用于token预算管理（请改用token-conservation工具）

Brooks's Law for Agents

Agent版布鲁克斯定律

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.

调度更多Agent并非总能带来帮助。协调开销随Agent数量增长：

Agent数量	预期开销	指导建议
1-3	可忽略不计	可自由调度
4-5	10-15%	可接受；需先规划
6-8	20-30%	需密切监控
9+	30%以上	可能产生反效果

协调开销以共享文件冲突率衡量：不同Agent对同一文件的并发读写操作占总Agent运行时间的百分比。

Post-Dispatch Review Checklist

调度后审查清单

After parallel agent runs, evaluate:

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

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

并行Agent运行完成后，需评估以下内容：

每个Agent是否产生了独特的成果？
总token消耗是否与价值成正比？
是否有Agent重复了其他Agent的工作？
使用更少的Agent是否能产生相同的结果？

如果有2个及以上问题的答案为“否”，则在未来同类调度中减少Agent数量。

Waste Signals

浪费信号

See

modules/waste-signals.md

for the 5 waste signal categories and detection criteria.

请查看

modules/waste-signals.md

了解5类浪费信号及检测标准。

Cross-References

交叉引用

.claude/rules/plan-before-large-dispatch.md

for the 4+ agent planning requirement

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

.claude/rules/plan-before-large-dispatch.md

：关于4个及以上Agent的规划要求

```
conserve:token-conservation
```
：会话级token预算管理
```
conjure:agent-teams
```
：调度协调