cost-estimate — Claude Code skill: what it does, how to install
This skill prices a repository, branch diff, or commit from code and Git evidence. Use it when an estimate needs scope, assumptions, and confidence.
npx skills add ulpi-io/skills --skill cost-estimate -a claude-codeWhat cost-estimate does
The skill resolves the target as a full repository, branch:<name>, or commit:<hash>, then measures the selected code surface with its helper scripts. It counts lines, files, languages, directories, and source categories, while Git history can provide session data. Source lines are assigned to productivity buckets before the calculator runs.
The report keeps raw engineering time separate from overhead and team multipliers. It can show calendar scenarios, engineering-only cost, full-team cost, effective lines per hour, and Claude ROI. Assumptions and confidence stay visible instead of being folded into one headline number. When Git history is unavailable, Claude ROI falls back to a LOC-based estimate.
The workflow runs as a forked analysis with its own reasoning budget. It uses Bash, Read, Glob, and Grep, plus the .py helpers under .agents/skills/cost-estimate/helpers/. This skill prices the work of building code; it does not budget hosted infrastructure, SaaS plans, or a project execution DAG.
What it helps with
- price an entire repository
- estimate effort for a branch diff
- measure the cost of one commit
- separate engineering time from team overhead
- calculate Claude ROI
Example prompts for the agent
- Estimate the current repository cost and list the assumptions.
- Estimate
branch:feat/foowith a breakdown by productivity category. - Price
commit:abc1234and include calendar time and Claude ROI.
How to install cost-estimate
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill cost-estimate -a claude-code2Manually: put the files in place
~/.claude/skills/cost-estimate/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/cost-estimate/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill cost-estimate -a codex2Manually: put the files in place
.agents/skills/cost-estimate/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill cost-estimate -a cursor2Manually: put the files in place
.cursor/skills/cost-estimate/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ulpi-io/skills cost-estimate2Manually: put the files in place
.github/skills/cost-estimate/SKILL.md1Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill cost-estimate -a gemini-cli2Platform CLI
gemini skills install https://github.com/ulpi-io/skills --path cost-estimateManually: put the files in place
.devin/skills/cost-estimate/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ulpi-io/skills --skill cost-estimate -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about cost-estimate
How do I install cost-estimate in Claude Code?
Run npx skills add ulpi-io/skills --skill cost-estimate -a claude-code, then check ~/.claude/skills/cost-estimate/SKILL.md.
What does cost-estimate do?
It measures a selected code scope, assigns source lines to productivity categories, and calculates engineering hours, overhead, team cost, and Claude ROI.
Can it estimate a branch or a commit?
Yes. Use branch:<name> or commit:<hash>; for those modes, the skill measures the relevant diff rather than the whole repository.
