Borrowing it
Nothing to install: this file belongs to Kandil7/prprompts-flutter-generator. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Kandil7/prprompts-flutter-generator/master/.claude/commands/planning/estimate-cost.mdgit clone --depth 1 https://github.com/Kandil7/prprompts-flutter-generatorWrote 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/kandil7/prprompts-flutter-generator/estimate-cost)<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/estimate-cost"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/estimate-cost/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kandil7/prprompts-flutter-generator/estimate-cost"><img src="https://agentmods.dev/badge/commands/kandil7/prprompts-flutter-generator/estimate-cost.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00012 | $0.03689 |
| Opus 5 | $0.00006 | $0.01844 |
| Sonnet 5 | $0.00002 | $0.00738 |
| Haiku 4.5 | $0.00001 | $0.00369 |
Grade A, and why
Estimate Project Cost 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 9d 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 — 444 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Cost Estimation from PRD
Overview
Analyze PRD metadata and generate comprehensive cost estimates including development hours, team costs, infrastructure, and third-party services.
Instructions
Step 1: Locate and Read PRD
# Expected location
docs/PRD.md
If not found, ask user for PRD location.
Step 2: Extract Key Metadata
Parse YAML frontmatter and extract:
Team Composition:
team_size(small/medium/large)team_composition.mobile.size,.junior,.mid,.seniorteam_composition.backend.sizeteam_composition.qa.sizeteam_composition.design.sizeteam_composition.security(if present)
Timeline:
business_context.timeline(total project duration)business_context.mvp_timeline(MVP duration)
Features:
featuresarray with complexity levels (low/medium/high/critical)- Count features by complexity
Technical Stack:
platforms(iOS, Android, Web, etc.)backend_type(REST, GraphQL, Firebase)auth_method(JWT, OAuth2, Firebase)offline_support(true/false)real_time(true/false)
Compliance:
compliancearray (HIPAA, PCI-DSS, GDPR, SOX, etc.)
Step 3: Calculate Development Hours
Use these baseline estimates per feature:
Feature Complexity Hours (per platform):
low: 40-80 hoursmedium: 80-160 hourshigh: 160-320 hourscritical: 320-640 hours
Platform Multipliers:
- iOS only: 1.0x
- Android only: 1.0x
- iOS + Android: 1.8x (code sharing via Flutter)
- iOS + Android + Web: 2.3x
- All platforms (6): 3.0x
Complexity Multipliers:
- Offline support: +30% hours
- Real-time features: +25% hours
- GraphQL backend: +15% hours
- Clean Architecture: +20% hours (upfront, saves 40% in maintenance)
Compliance Multipliers:
- HIPAA: +40% (audit logs, encryption, BAA documentation)
- PCI-DSS: +35% (tokenization, security audits, SAQ compliance)
- SOX: +30% (financial controls, audit trails)
- GDPR: +20% (data deletion, consent flows, privacy policy)
- COPPA: +25% (parental consent, age gates)
- FERPA: +20% (education data protections)
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.
- 9d ago First seen · 444 lines · 12 tokens per session scan A 8149ceb7facb
Estimate Project Cost is a command published in the GitHub repository Kandil7/prprompts-flutter-generator (11 stars, last pushed 9mo ago), licensed MIT. It adds 12 tokens to every session and 3,689 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
speckit.gh-triage.triage
Fetch open GitHub issues, classify each as bug, feature, or chore, then DELEGATE to the correct extension: bugs → bug.fetch (saved under .specify/bugs/), chores → chore.fetch (saved under .specify/chores/), features → speckit.specify (saved under specs/). Never save bugs or chores as specs.
speckit.chore.fetch
Load an existing GitHub issue into the chore workflow and seed a triage draft.
speckit.chore.implement
Implement the scoped chore (the actual maintenance work) and record what changed.
speckit.bug.issue
File a GitHub issue from a bug assessment (the 'report' phase) and record the issue link.
speckit.chore.issue
File a GitHub issue from a chore assessment (the 'report' phase) and record the issue link.
speckit.gh-triage.feature
Create a GitHub issue describing a new feature, label it with the configured feature label, and optionally auto-run speckit.specify to turn it into a spec.