worker-budgetlisted

Use BEFORE spawning any Agent worker for substantial work (builds, audits, releases). Deterministic budget analysis — pricing snapshot, per-worker-class token forecast from observed history, tier recommendation, and a worker contract with success thresholds + orchestrator-escalation triggers. Also use when the user asks about worker costs, budget analysis, or model-tier selection.
esummervill/worker-budget · ★ 0 · AI & Automation · score 72

Install: claude install-skill esummervill/worker-budget

# Worker budget + designation system Applies a delegation-tiering doctrine mechanically: no big model on mundane work, no small model planning, and the **orchestrator woken only at mediation points**. The system itself follows the deterministic-shell pattern — arithmetic is a script, and the ONLY model involvement is a small-model scout (Haiku) for the two genuinely fuzzy inputs: price verification when stale, and task-complexity classification when novel. ## Flow (each time workers are about to be spawned) 1. **Run the deterministic budgeter** (no model, no network): ```bash node ~/.claude/skills/worker-budget/scripts/budget.mjs <worker-class> [count] ``` Worker classes: `build-heavy`, `build-standard`, `cartography`, `research`, `release`, `verify`, `grind`. Output: cost estimate per tier, recommended tier, staleness warning, and a filled worker-contract template. 2. **If output says `PRICING STALE`** (snapshot older than the configured window): spawn ONE Haiku scout (`model: haiku`) with exactly this brief: "Fetch current Claude API per-MTok pricing for Opus, Sonnet, Haiku from docs.anthropic.com (WebSearch/WebFetch). Return ONLY a JSON object matching the schema in ~/.claude/skills/worker-budget/scripts/pricing.json — same keys, updated prices, as_of today. No prose." Then write its JSON over pricing.json and re-run the budgeter. Never let a large model do this errand; never trust remembered pricing. 3. **If the task fits no e