skill-cost-projections

You can forecast workflow spend by reading per-step cost averages from ~/.claude-octopus/metrics or legacy metrics-tracker.sh outputs, then projecting remaining spend and displaying the results in the HUD with optional budget ceiling checks.

Tracking budget overruns in Claude Octopus workflows is done by setting an optional budget ceiling; the skill compares your projected total spend against this ceiling as steps complete and displays warnings in the HUD if the forecast exceeds the limit.

Yes, you can use this cost projection tool with incomplete metrics because it handles insufficient data gracefully, ensuring the HUD still displays partial projections without crashing when per-step averages cannot be fully calculated.

The skill supports multiple data sources by reading workflow metrics from both the current ~/.claude-octopus/metrics directory and legacy metrics-tracker.sh script outputs to compute per-phase cost averages.

To start predicting real-time workflow spend, simply ask the skill to project costs for the current active Claude Octopus workflow; it will automatically calculate the average cost per completed step and forecast the remaining budget.