budget-estimator
Estimate API costs for a planned pipeline or for an entire script before any generation runs. Reads pipeline SPEC.md(s), the storyboard, and `brief/tools-and-models.md`, then projects cost per shot and total — with a low / typical / high range that accounts for take iteration. Writes a budget report to `budgets/estimate-<YYYY-MM-DD>.md`. Use before `/run-pipeline` on any non-trivial project.
Works with
--- name: budget-estimator description: Estimate API costs for a planned pipeline or for an entire script before any generation runs. Reads pipeline SPEC.md(s), the storyboard, and `brief/tools-and-models.md`, then projects cost per shot and total — with a low / typical / high range that accounts for take iteration. Writes a budget report to `budgets/estimate-<YYYY-MM-DD>.md`. Use before `/run-pipeline` on any non-trivial project. license: MIT --- # Budget estimator You produce realistic cost projections for an AI video project. ## Inputs - Either a single pipeline (`pipelines/<name>/SPEC.md`) or all of them. - `scripts/storyboards/` for shot count and durations. - `brief/tools-and-models.md` for model + provider per stage. - Latest pricing — pull from `research/models-*.md` if recent (≤30 days), otherwise re-fetch from provider pages. ## Cost model For each shot, for each pipeline stage: - **Per-call cost** — what one generation costs. - **Iteration multiplier** — how many takes the user typically runs to get an acceptable result. Defaults if no project history: - Text-to-image: ×3 (cheap, iterate freely) - Image-to-video: ×2 (expensive, iterate sparingly) - Text-to-video direct: ×3 (drifts; expect retries) - Voice: ×1.5 - Lip-sync: ×1.5 - Upscale / interpolate: ×1 - **Typical / low / high** = (1 × per-call), (multiplier × per-call), (multiplier × 1.5 × per-call). If `logs/production-log.md` has past data on this project, use the actual observed iteration count instead of defaults. ## Output `budgets/estimate-<YYYY-MM-DD>.md`: ``` # Cost estimate — <project name> Date: <YYYY-MM-DD> Pricing source: <date pulled, provider pages> ## Per-shot breakdown | Shot | Pipeline | Stages | Low | Typical | High | |------|----------|--------|-----|---------|------| ## Totals - Low (everything first-take): $X.XX - Typical: $Y.YY - High (heavy iteration): $Z.ZZ ## Sensitivity - Single biggest cost driver: <stage / model> - Cheapest substitute that preserves quality: <if any> ## Assumptions - <list: aspect, duration per shot, iteration multipliers used, currency> ``` After writing, summarise in 4-6 lines and flag if the typical figure exceeds the user's stated budget. ## Discipline - Always show a range, never a single point estimate. - Always cite the date the prices came from. Surface explicitly that AI media pricing changes monthly. - Convert all prices to a single currency (default USD; user can override). - Don't include human time. This is API spend only. - If a stage's pricing model is "per second of output", multiply by the storyboard duration for that shot, not the wall-clock generation time.
More Project Management skills
firecrawl-build-onboarding
firecrawl/skills
Get Firecrawl credentials and SDK setup into a project. Use when an application needs `FIRECRAWL_API_KEY`, when an agent should add Firecrawl to `.env`, when the user wants to authenticate Firecrawl for app code, or when choosing the first SDK and docs for a new Firecrawl integration. This skill includes its own browser auth flow, so it does not depend on the website onboarding skill.
email-sequence
coreyhaines31/marketingskills
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding-cro.
onboard
pbakaus/impeccable
Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.

