Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/superclaude-org/superclaude_framework/estimategit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_FrameworkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/superclaude-org/superclaude_framework/estimate)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/estimate"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/estimate.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00015 | $0.00743 |
| Opus 5 | $0.00008 | $0.00371 |
| Sonnet 5 | $0.00003 | $0.00149 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
estimate scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:estimate - Development Estimation
Triggers
- Development planning requiring time, effort, or complexity estimates
- Project scoping and resource allocation decisions
- Feature breakdown needing systematic estimation methodology
- Risk assessment and confidence interval analysis requirements
Usage
/sc:estimate [target] [--type time|effort|complexity] [--unit hours|days|weeks] [--breakdown]
Behavioral Flow
- Analyze: Examine scope, complexity factors, dependencies, and framework patterns
- Calculate: Apply estimation methodology with historical benchmarks and complexity scoring
- Validate: Cross-reference estimates with project patterns and domain expertise
- Present: Provide detailed breakdown with confidence intervals and risk assessment
- Track: Document estimation accuracy for continuous methodology improvement
Key behaviors:
- Multi-persona coordination (architect, performance, project-manager) based on estimation scope
- Sequential MCP integration for systematic analysis and complexity assessment
- Context7 MCP integration for framework-specific patterns and historical benchmarks
- Intelligent breakdown analysis with confidence intervals and risk factors
MCP Integration
- Sequential MCP: Complex multi-step estimation analysis and systematic complexity assessment
- Context7 MCP: Framework-specific estimation patterns and historical benchmark data
- Persona Coordination: Architect (design complexity), Performance (optimization effort), Project Manager (timeline)
Tool Coordination
- Read/Grep/Glob: Codebase analysis for complexity assessment and scope evaluation
- TodoWrite: Estimation breakdown and progress tracking for complex estimation workflows
- Task: Advanced delegation for multi-domain estimation requiring systematic coordination
- Bash: Project analysis and dependency evaluation for accurate complexity scoring
Key Patterns
- Scope Analysis: Project requirements → complexity factors → framework patterns → risk assessment
- Estimation Methodology: Time-based → Effort-based → Complexity-based → Cost-based approaches
- Multi-Domain Assessment: Architecture complexity → Performance requirements → Project timeline
- Validation Framework: Historical benchmarks → cross-validation → confidence intervals → accuracy tracking
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 88 lines · 15 tokens per session scan A fe772a89d263
estimate is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,866 stars, last pushed 13d ago), licensed MIT. It adds 15 tokens to every session and 743 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
estimate
Provide development estimates for tasks, features, or projects with intelligent analysis.
task
Execute complex tasks with intelligent workflow management and delegation.
spawn
Meta-system task orchestration with intelligent breakdown and delegation.
index
Generate comprehensive project documentation and knowledge base with intelligent organization.
reflect
Task reflection and validation using Serena MCP analysis capabilities.
select-tool
Intelligent MCP tool selection based on complexity scoring and operation analysis.