cost-estimate

Estimate development cost of a codebase and output structured JSON.

13|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/ulpi-io/browse --skill cost-estimate-ulpi-io
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cost-estimate
Source: https://github.com/ulpi-io/browse/tree/main/.agents/skills/cost-estimate
Command: npx skills add https://github.com/ulpi-io/browse --skill cost-estimate-ulpi-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Cost Estimate Skill computes a clear, data-driven development cost for a given codebase by analyzing lines of code, project scope, and complexity, delivering a structured plan for budgeting and planning.

Core Features & Use Cases

  • Branch-diff cost estimation: evaluate the added effort from a feature branch compared to a base branch.
  • Full-repo budgeting: estimate total engineering hours and costs for the entire repository.
  • ROI-focused planning: project Claude ROI, calendar time, and team costs to guide buy-vs-build decisions.
  • Use Case: A product team wants to forecast engineering costs across multiple modules before starting a major rewrite.

Quick Start

Invoke the cost-estimate command on your repository to generate a cost breakdown for the full codebase, a branch diff, or a single commit.

Frequently Asked Questions about cost-estimate

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

FAQPage Schema
How do I estimate development cost from lines of code in a git repository?▼

To estimate development cost from lines of code, this Skill analyzes your git repository scope, applies productivity rates and market rates by role, and outputs a structured JSON payload with total engineering hours and costs. It handles full-repo, branch diff, or single commit scopes.

Can I calculate the ROI and calendar time for a feature branch compared to a base branch?▼

Yes, you can calculate ROI and calendar time for a feature branch using branch-diff cost estimation. It evaluates the added effort compared to a base branch, projecting Claude ROI, team costs, and calendar time to guide your buy-vs-build decisions.

What is the best way to forecast engineering hours and budget for a full codebase rewrite?▼

The best way to forecast engineering hours for a full codebase rewrite is full-repo budgeting. This Skill computes total engineering hours and costs by analyzing lines of code, project scope, and complexity to deliver a structured plan for budgeting.

Does the cost calculator support single-commit scoping with specific qualifiers like branch names?▼

Yes, the cost calculator supports single-commit scoping with optional qualifiers like branch:feat/foo or commit:abc1234. It applies configurable overhead multipliers and market rates to generate a structured JSON breakdown for downstream reporting.

What inputs do I need to generate a cost breakdown for software engineering planning?▼

You need a git repository target, such as a full repo, branch diff, or commit hash. The Skill then applies configurable productivity rates, overhead multipliers, and market rates by role to output a structured cost breakdown for planning.