Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Read accumulated cost-tracking spend + budget config, compute utilization, emit 50/75/90/100% alert ladder
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | -38% | 0% |
| case-11 | ✗→✓ | ▲ Improved | 7% | 0% |
| case-03 | ✗→✓ | ▲ Improved | -12% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -37% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -17% | 0% |
Reads cost-tracking:budget-config for the project's budget limit, sums total_cost_usd across session-* records produced by cost-track, computes utilization, and emits the measured 4-tier alert ladder (50% INFO / 75% WARNING / 90% CRITICAL / 100% HARD_STOP).
Until P2 (this skill) landed, the README documented the alert ladder but no code checked it. Now this skill is the gate.
/cost-optimize first./loop 30m for continuous monitoring.bash node plugins/ruflo-cost-tracker/scripts/budget.mjs check
Filter by period: BUDGET_PERIOD=today (default all). Use BUDGET_QUIET=1 for machine-readable JSON.
bash node plugins/ruflo-cost-tracker/scripts/budget.mjs set 50.00 node plugins/ruflo-cost-tracker/scripts/budget.mjs get
budget.mjs check exits with code 1 when utilization ≥ 100%. Wrap critical agent spawns in a budget.mjs check && spawn … guard to fail closed.cost-tracking:budget-config)json{ "budget_usd": 50.00, "setAt": "2026-05-05T...", "thresholds": { "info": 0.50, "warning": 0.75, "critical": 0.90, "hard_stop": 1.00 } }
| Threshold | Level | Action | |---|---|---| | 50% | INFO 🟡 | log notification, no UX disruption | | 75% | WARNING 🟠 | display warning, suggest /cost-optimize | | 90% | CRITICAL 🔴 | urgent alert, recommend model downgrades | | 100% | HARD_STOP 🛑 | halt non-essential spawns; exit code 1 |
cost-track (producer) — populates cost-tracking:session-*cost-report — same data source, narrative formatcost-optimize — recommended action when WARNING/CRITICALOther measured skills in the registry, with their headline benchmark lift.