fan-out-cost-control

Controls parallel agent fan-out cost through model selection, bounded context, and nested consultation limits.

3|Updated May 8, 2026
One-click install
npx skills add https://github.com/wan-huiyan/agent-traffic-control --skill fan-out-cost-control-wan-huiyan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: fan-out-cost-control
Source: https://github.com/wan-huiyan/agent-traffic-control/tree/main/plugins/agent-traffic-control/skills/fan-out-cost-control
Command: npx skills add https://github.com/wan-huiyan/agent-traffic-control --skill fan-out-cost-control-wan-huiyan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Parallel agent fan-outs can silently exceed their intended budget: launchers inherit expensive parent models, helpers forward every worker transcript to premium reviewers, and repeated turns reprocess large contexts. This Skill provides a discipline for planning, bounding, and auditing the real cost of multi-agent investigations. ## Core Features & Use Cases - Deliberate model and scale selection: Verify launcher model inheritance, state model/tier, effort, and agent count ceilings before launch, and match model strength to task uncertainty. - Consultation multiplication control: Detect helpers that forward transcripts to stronger models, aggregate shard evidence before commissioning shared reviews, and cap nested agent work. - Context and checkpoint management: Choose between resuming large histories versus spawning focused helpers, and have workers save independently usable partial results with atomic writes. - Outcome auditing: Compare planned versus actual model, width, and cost; verify saved evidence; and avoid converting bounded searches into false claims of impossibility. - Use Case: A coordinator launches extraction workers that each invoke a premium reviewer, blowing the budget despite correct output. Use this Skill to verify launcher inheritance, cap nested consultations, and review combined evidence instead. ## Quick Start Ask the agent to plan a parallel investigation with an explicit model tier, agent count ceiling, and checkpoint policy before launching any workers.

Frequently Asked Questions about fan-out-cost-control

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I control costs when running parallel AI agents?▼

State the model tier, reasoning effort, and agent count ceiling before launching, and verify the launcher does not silently inherit an expensive parent model. Cap nested consultations and aggregate shard evidence before commissioning shared premium reviews.

Why does my multi-agent run cost more than the agent count suggests?▼

Hidden costs come from helpers forwarding each worker transcript to stronger models, standing review preferences applied inside every shard, and repeated turns reprocessing large contexts. Inspect calls made by children and consultation tools, not just the root's visible agent count.

Should I resume a large agent history or start a fresh helper?▼

Compare the remaining work against the evidence needed: a new helper with a focused brief can cost less than resuming a large history, but continuing is cheaper when the active worker holds irreplaceable context. Do not habitually always restart or always resume.

How do I preserve partial work from long-running agents?▼

Ask workers to save independently usable results as they complete, with exact input identities and completion state, using separate files or atomic replacement to avoid writer collisions. Arrange checkpointing before launch, and never expose a partial artifact as complete.

When should I stop a parallel investigation?▼

Honor explicit stop or budget limits, and within authorization weigh saved progress against remaining cost—sunk cost is not a reason to continue. Save what can be saved safely, record the real continuation state, and do not turn a bounded search into a claim that no solution exists.