estimate
Skill46 starsChanged 31 days agoMITView on GitHub
Predict the dollar cost of a coding task across Opus 4.7, Sonnet 4.6, and Haiku 4.5 BEFORE the user runs it. Pure heuristic + historical-anchor math, zero LLM calls. Use when the user asks "how much will X cost?", "is this task worth doing on Opus?", "estimate the refactor", or any pre-flight pricing question.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- mehboobali98/rmine-skillstheir own version, first seen Nov 6, 2026
- striderZA/OpenCodeGameStudiostheir own version, first seen Nov 4, 2026
- Donchitos/Claude-Code-Game-Studiostheir own version, first seen Oct 19, 2026
- venus2099/codex-game-studiostheir own version, first seen Oct 17, 2026
- anis-dr/skillstheir own version, first seen Oct 15, 2026
- ShiningPlague/shiningplague-studiotheir own version, first seen Oct 11, 2026
Used with
Projects with it also use team-audio, playtest-report and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CoralGameSkillteam-audio
Orchestrate audio team: audio-director + sound-designer + technical-artist + gameplay-programmer for full audio pipeline from direction to implementation.
Also in 13 projects that use this
CoralGameSkillplaytest-report
Generates a structured playtest report template or analyzes existing playtest notes into a structured format. Use this to standardize playtest feedback collection and analysis.
Also in 12 projects that use this
lilangMaxSkillasset-spec
Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Also in 10 projects that use this
lilangMaxSkillcreate-control-manifest
After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Also in 10 projects that use this
- +3 more from CoralGame
- +5 more from lilangMax
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- Donchitos/Claude-Code-Game-Studios★ 27ksame name
- pixel-cellar/Claude-Code-Game-Studios★ 324same name
- striderZA/OpenCodeGameStudios★ 118same name
- tranhieutt/software_development_department★ 71same name
- cenconq25/claude-code-app-studio★ 40same name
- CoralGame/Claude-Code-Game-Studios★ 19same name
- dawn840705/codex-code-studios★ 17same name
- CodePhobiia/claude-roblox-game-studio★ 9same name
- lilangMax/ClaudeCodeGameStudios★ 8same name
- viknesh20-20/claude-code-tool-kit★ 7same name
18 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Call the sipcode:estimate_task_cost MCP tool with:
- Distinctive: line 17
Never invent precision. Round to whole cents unless the estimate is sub-$0.10.
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Sipcode — Estimate (pre-flight cost prediction)
Call the sipcode:estimate_task_cost MCP tool with:
task: natural-language task description (≥3 chars). Example:"refactor the auth pipeline across 6 files".cwd: absolute path to the project root the task will run in. If the user didn't specify a directory, ask before calling.
The tool returns per-model dollar predictions with a confidence band.
When presenting:
- Show all three models (Opus / Sonnet / Haiku) side-by-side, not just the most expensive.
- Surface the confidence band — if it's wide, say so honestly. If the tool reports
confidence: "low"because no past sessions matched this complexity tier, mention that the estimate is heuristic-only. - Make a model recommendation grounded in the cost spread. If Haiku is within ~10% of Sonnet for the task, recommend Haiku. If the task complexity is high (5+ files), Opus is usually worth the cost.
- Never invent precision. Round to whole cents unless the estimate is sub-$0.10.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

