How do I install the Cost Projection skill?

Run npx skillmds@latest add gabrielmoreira/cost-projection in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Cost Projection safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Cost Projection?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Cost Projection free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Cost Projection?

gabrielmoreira (@gabrielmoreira) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Cost Projection by gabrielmoreira — Agent Skill

Name: Cost Projection
Rating: 4.2 (5 reviews)
Author: gabrielmoreira

Cost Projection

Forward-looking spend extrapolation. Computes a USD-per-day rate from the recent measurement window, projects to 7d/30d/90d/365d horizons, and surfaces "days until budget exhausted" when a budget is configured. Predictive counterpart to `cost-budget-check` (reactive).

gabrielmoreira Updated Sep 9, 2026 17 repo stars

File contents

Forward-looking cost projection that pairs with cost-budget-check:

cost-budget-check answers "have we crossed the line?" — reactive
cost-projection answers "when will we cross the line?" — predictive

Algorithm

Read all session-* records from the cost-tracking namespace (same source cost-budget-check uses).
Filter to a measurement window (default last 7 days on capturedAt/startedAt).
Compute the per-day burn rate: windowSpend / windowDays.
Linear-extrapolate to each requested horizon (default 7d/30d/90d/365d).
If a budget is configured (budget-config key set by cost-budget set):
- Compute "days until 75% / 90% / 100% consumed" at the current rate.
- Surface as a separate table block with ALREADY REACHED markers for thresholds already exceeded.

Flags

--window Measurement window. Nh|Nd|Nw|Nm. Default 7d. --horizons Projection horizons. Default 7d,30d,90d,365d. --format table|json Default table (markdown).

Env: PROJECTION_NAMESPACE override (default cost-tracking), PROJECTION_QUIET=1 (alias for --format json).

Smoke transcript (3 sessions × $1 over 7d, $20 budget)

| Sessions in window | 3 |
| Window spend | $3.000000 |
| **USD per day** | **$0.428571** |
| All-time spend | $3.000000 across 3 sessions |

## Projected spend (linear extrapolation)
| Horizon | Days | Projected spend |
|---|---:|---:|
| 7d | 7 | $3.0000 |
| 30d | 30 | $12.8571 |

## Budget exhaustion ($20.00 configured)
| Threshold | Target | Remaining | Time at current rate |
|---|---:|---:|---|
| 75% | $15.00 | $12.00 | 28.0 days |
| 90% | $18.00 | $15.00 | 35.0 days |
| 100% | $20.00 | $17.00 | 39.7 days |

When to use

Finance / SRE planning: hand the JSON output to a budget dashboard for "are we on track for the quarter?".
CI gates: cost-projection --format json | jq '.budget.exhaustion[2].daysUntilReached < 7' → fail builds when 100% exhaustion is < 1 week away.
Post-workload-shift sanity check: after a big feature lands, re-run to verify the rate hasn't accelerated past expectations.

Stationarity assumption

Linear extrapolation assumes the current rate holds. The footer reminds operators to re-run after workload shifts. For drift detection over MULTIPLE windows, pair with cost-trend (which already covers benchmark-drift).

---name: cost-projectiondescription: Forward-looking spend extrapolation. Computes a USD-per-day rate from the recent measurement window, projects to 7d/30d/90d/365d horizons, and surfaces "days until budget exhausted" when a budget is configured. Predictive counterpart to `cost-budget-check` (reactive).--- Forward-looking cost projection that pairs with `cost-budget-check`: - **`cost-budget-check`** answers "have we crossed the line?" — reactive - **`cost-projection`** answers "when will we cross the line?" — predictive ## Algorithm 1. Read all `session-*` records from the `cost-tracking` namespace (same source `cost-budget-check` uses). 2. Filter to a measurement window (default last 7 days on `capturedAt`/`startedAt`). 3. Compute the per-day burn rate: `windowSpend / windowDays`. 4. Linear-extrapolate to each requested horizon (default 7d/30d/90d/365d). 5. If a budget is configured (`budget-config` key set by `cost-budget set`): - Compute "days until 75% / 90% / 100% consumed" at the current rate. - Surface as a separate table block with `ALREADY REACHED` markers for thresholds already exceeded. ## Flags --window <duration> Measurement window. `Nh|Nd|Nw|Nm`. Default `7d`. --horizons <csv> Projection horizons. Default `7d,30d,90d,365d`. --format table|json Default `table` (markdown). Env: `PROJECTION_NAMESPACE` override (default `cost-tracking`), `PROJECTION_QUIET=1` (alias for `--format json`). ## Smoke transcript (3 sessions × $1 over 7d, $20 budget) ``` | Sessions in window | 3 | | Window spend | $3.000000 | | **USD per day** | **$0.428571** | | All-time spend | $3.000000 across 3 sessions | ## Projected spend (linear extrapolation) | Horizon | Days | Projected spend | |---|---:|---:| | 7d | 7 | $3.0000 | | 30d | 30 | $12.8571 | ## Budget exhaustion ($20.00 configured) | Threshold | Target | Remaining | Time at current rate | |---|---:|---:|---| | 75% | $15.00 | $12.00 | 28.0 days | | 90% | $18.00 | $15.00 | 35.0 days | | 100% | $20.00 | $17.00 | 39.7 days | ``` ## When to use - **Finance / SRE planning**: hand the JSON output to a budget dashboard for "are we on track for the quarter?". - **CI gates**: `cost-projection --format json | jq '.budget.exhaustion[2].daysUntilReached < 7'` → fail builds when 100% exhaustion is < 1 week away. - **Post-workload-shift sanity check**: after a big feature lands, re-run to verify the rate hasn't accelerated past expectations. ## Stationarity assumption Linear extrapolation assumes the current rate holds. The footer reminds operators to re-run after workload shifts. For drift detection over MULTIPLE windows, pair with `cost-trend` (which already covers benchmark-drift).

Frequently asked questions