cost-health

The four CI-gate skills (budget / burn / anomaly / projection) each answer a different question. This skill composes them — runs all four IN PARALLEL, returns max(exit_codes), prints a one-line summary per check.

Algorithm

Implementation: scripts/health.mjs.

1. Spawn all four subcheck scripts in parallel (Promise.all over child_process.spawn).
2. Each subcheck emits --format json; parse and capture exit code.
3. Projection has no built-in exit code — synthesize one from daysUntilReached[100%] < --alert-days-to-exhaust.
4. Final exit code = max(subcheck exits). Any single failure fails the gate.
5. Print one-line summary per check + overall HEALTHY/UNHEALTHY badge.

CI integration

- name: Cost health gate
  run: cost health --alert-acceleration 100 --alert-outliers 1

A single step covers four alert ladders. Before this skill you'd wire four separate gates that each duplicated the npx + memory-list overhead; now it's one shell-out (and the four subcheck npx calls run in parallel internally).

Customizing thresholds

# Quarterly review — stricter thresholds
cost health

Smoke transcript (5 healthy sessions, then add 1 outlier)

Skipping subchecks

Useful when:

• A subcheck doesn't apply (no budget set → skip projection)
• A subcheck is too slow for fast-feedback contexts (smoke runs)
• A subcheck is being independently CI-gated already

Exit code semantics

max() means the worst signal wins — exit 2 (config error) always dominates exit 1 (alert), so you spot misconfigured pipelines before they masquerade as healthy.