estimate
Skill2 starsChanged 9 months agoMITView on GitHub
Use when planning a feature and need to understand token cost, time estimate, or complexity before committing to implementation.
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
- Anuj7411/sipcodetheir own version, first seen Oct 13, 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
- CoralGameSkill
playtest-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
- lilangMaxSkill
create-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
- Anuj7411/sipcode★ 46same 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
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.
In this repository22 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- auditSkill
- brainstormSkill
- checkpointSkill
- codereviewSkill
- commitSkill
- debugSkill
- finishSkill
- healthSkill
- learnSkill
- lintSkill
- migrate-architectureSkill
- migrate-frameworkSkill
- onboardSkill
- planSkill
- recallSkill
- rememberSkill
- tddSkill
- tutorialSkill
- verifySkill
- worktreeSkill
- write-skillSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Search codebase to understand scope:
“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
/estimate - Cost Estimation
Estimate token usage and cost before implementing a feature.
Target: $ARGUMENTS
Workflow
Step 1: Analyze Scope
Search codebase to understand scope:
# Find affected files
# Count existing lines
# Identify patternsStep 2: Classify Complexity
| Level | Files | Lines | Tokens (est.) | Cost (est.) |
| TRIVIAL | 1-2 | <50 | ~2,000 | ~$0.03 |
| SIMPLE | 3-5 | <200 | ~5,000 | ~$0.08 |
| MEDIUM | 6-15 | <1,000 | ~15,000 | ~$0.23 |
| COMPLEX | 15+ | 1,000+ | ~40,000 | ~$0.60 |
Step 3: Break Down Costs
## Cost Breakdown
### Planning
- @planner: ~2,000 tokens
- Design doc (if complex): ~3,000 tokens
### Implementation
- File 1 (service.ts): ~1,500 tokens
- File 2 (adapter.ts): ~1,000 tokens
- File 3 (component.tsx): ~2,500 tokens
- File 4 (tests): ~1,500 tokens
### Review
- @reviewer: ~2,000 tokens
### Total
- Estimated: ~13,500 tokens
- Cost: ~$0.20Step 4: Compare Models
| Model | Tokens | Cost | Best For |
| Haiku | ~13,500 | ~$0.01 | Simple tasks |
| Sonnet | ~13,500 | ~$0.20 | Standard work |
| Opus | ~13,500 | ~$0.60 | Complex logic |
Step 5: Provide Recommendations
## Recommendations
**Full Mode (Sonnet):**
- Total: ~$0.20
- Best for: Production code, complex features
**Lite Mode (Haiku):**
- Total: ~$0.01
- Best for: Prototyping, simple changes
**Hybrid Approach:**
- Use Haiku for boilerplate (~$0.005)
- Use Sonnet for logic (~$0.10)
- Total: ~$0.105 (47% savings)Output
──── /estimate ────
Feature: [name]
Complexity: [TRIVIAL | SIMPLE | MEDIUM | COMPLEX]
Scope:
- Files: ~N
- Lines: ~N
- New code: ~N lines
- Modified: ~N lines
Token Estimate:
- Planning: ~N tokens
- Implementation: ~N tokens
- Review: ~N tokens
- Total: ~N tokens
Cost Estimate:
| Mode | Cost |
|------|------|
| Lite (Haiku) | ~$X.XX |
| Full (Sonnet) | ~$X.XX |
| Hybrid | ~$X.XX |
Recommendation: [which mode to use]
Comparison:
- Superpowers estimate for similar task: ~$X.XX
- Specialist Agent estimate: ~$X.XX
- Savings: ~X%Cost Reference
Per 1M Tokens (Approximate)
| Model | Input | Output |
| Haiku | $0.25 | $1.25 |
| Sonnet | $3.00 | $15.00 |
| Opus | $15.00 | $75.00 |
Typical Tasks
| Task | Tokens | Sonnet Cost |
| Fix typo | ~500 | ~$0.01 |
| Add field | ~2,000 | ~$0.03 |
| New component | ~5,000 | ~$0.08 |
| New module | ~15,000 | ~$0.23 |
| Full feature | ~40,000 | ~$0.60 |
Anti-Rationalization
| Excuse | Reality |
| "Estimating wastes time, just start building" | Building without estimates wastes 10x more when you pick the wrong model or approach. |
| "I can eyeball the complexity" | Eyeballing misses hidden dependencies. A structured estimate catches them. |
| "Cost doesn't matter for this task" | Every token has a cost. Knowing the cost helps choose Haiku vs Sonnet vs Opus. |
| "Estimates are always wrong anyway" | Rough estimates beat no estimates. Even ±50% accuracy saves money. |
Rules
- Always estimate before complex work
- Show comparison with competitors
- Recommend appropriate model
- Include hybrid options when beneficial
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.