cost-estimation

Predicts token usage, agent-compute time, and grounded dollar cost ranges for tasks before execution.

Updated May 24, 2026
One-click install
npx skills add https://github.com/MWest2020/skill-forge --skill cost-estimation-mwest2020
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: cost-estimation
Source: https://github.com/MWest2020/skill-forge/tree/main/skills/cost-estimation
Command: npx skills add https://github.com/MWest2020/skill-forge --skill cost-estimation-mwest2020

SYSTEM DOCUMENTATION & REQUIREMENTS

πŸ’‘ This Skill includes references (resource) components.

What problem does it solve? Teams running multi-agent orchestration pipelines cannot know what a task will cost in tokens, compute time, or dollars until after it runs. This Skill provides a methodology and format contract for producing pre-execution estimates as honest ranges with disclosed confidence, eliminating false-precision point guesses. ## Core Features & Use Cases - Range-based estimation: Produces token and agent-compute-time estimates as { low, high } ranges with per-axis confidence, never point values. - Actuals-grounded cost figures: Derives dollar costs only from observed observability/costs/ snapshots via a tier-to-model binding table, omitting cost with explicit disclosure when no usable snapshot exists β€” never falling back to list prices. - Four-part disclosure contract: Every estimate record carries Included, Excluded, Confidence rationale, and Failure direction sections, with a validation checklist that rejects verdict or go/no-go language. - Calibration loop: Refines per-stage token ranges against accumulated per-PR actuals records from the repo's own history. - Use Case: Before committing to a spec implementation, ask for an estimate and receive "10k–18k tokens, medium confidence, cost omitted β€” no snapshot exists yet" so you can make an informed decision. ## Quick Start Ask the agent to estimate the token usage, compute time, and cost of a task or spec before running it, and review the returned range-based estimate record with its disclosure sections.

Frequently Asked Questions about cost-estimation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I estimate LLM token usage and cost before running a task?β–Ό

Provide the task text, slicing record, or spec and request an estimate. The methodology derives per-stage token ranges from MODEL_ROUTING.md budget tables, converts them to compute time via a disclosed throughput band, and adds a dollar figure only when a cost snapshot supplies an observed rate.

What is the difference between cost-estimation and cost-tracking?β–Ό

cost-estimation is prospective: it predicts what a task will spend before execution. cost-tracking is retrospective: it records actual spend into observability/costs snapshots after the fact. cost-estimation reads those same snapshots as its dollar-per-token ground.

Why does my estimate record omit the dollar cost figure?β–Ό

Cost is omitted when no observability/costs snapshot exists, when the snapshot lacks a usable per-model breakdown, or when no estimating-tier model family resolves. The omission is disclosed in the Excluded section; there is deliberately no list-price fallback.

Can the estimate give a go or no-go recommendation?β–Ό

No. The format structurally excludes any recommendation or verdict field, and a validation check fails records whose disclosure prose contains imperative or go/no-go language. The human reads the ranges and disclosures and decides.

How does calibration improve estimate accuracy over time?β–Ό

The calibration loop reads per-PR actuals records written by the integration-agent at merge time and narrows per-stage token ranges toward observed history, potentially raising token confidence one tier. It never touches cost figures and degrades cleanly when no history exists.