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/jonase47/ccpr/p1-financial-plangit clone --depth 1 https://github.com/jonase47/ccprWrote 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/jonase47/ccpr/p1-financial-plan)<a href="https://agentmods.dev/commands/jonase47/ccpr/p1-financial-plan"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p1-financial-plan.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.1 | $0.00000 | $0.01088 |
| Opus 5 | $0.00000 | $0.00544 |
| Sonnet 5 | $0.00000 | $0.00218 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
p1-financial-plan 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 2d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p1-financial-plan – Cost Structure, Revenue Forecast & Break-Even
Creates a first financial plan with Cost Structure, Revenue Forecast, and break-even analysis. The goal is not exact bookkeeping but a plausible set of numbers that demonstrates the economic viability of the venture.
Argument: $ARGUMENTS = [Planning horizon, e.g. "3 years", "18 months"]
If provided: Create the financial plan for the specified period. If not provided: Ask for the desired planning horizon. The default would be 3 years – confirm this suggestion or allow it to be adjusted.
Execution
1. Read Context
Read the following files (if available):
- DISCOVERY.md (market assessment, willingness to pay)
- BUSINESS_MODEL.md (revenue streams, pricing, Cost Structure from Canvas)
- MVP.md (scope – influences development costs)
- FEATURES.md (scope – influences Operating Costs)
2. Delegate to business-analyst Agent (Lead)
Delegate the entire financial planning to the business-analyst agent:
Create a financial plan for the horizon: $ARGUMENTS Context from BUSINESS_MODEL.md: [Insert revenue streams, pricing, Cost Structure]
The financial plan must include:
A. Cost Structure (one-time & ongoing)
- Development costs (person-months × day rate or hourly rate)
- Infrastructure/hosting per month (minimum, growth)
- Tools, licences, software
- Marketing/sales
- Overhead (accounting, legal, etc.)
B. Revenue Forecast (3 scenarios)
- 🐻 Bear Case: What if things go worse than expected?
- 📊 Base Case: Realistic expectation
- 🚀 Bull Case: What if things go significantly better?
- For each scenario: number of customers/users per month + revenue
C. Break-Even Analysis
- When is the monthly break-even reached (Base Case)?
- How many paying customers/users are needed for this?
D. Capital Requirements
- How much capital is needed until break-even?
- Recommendation: self-financing / debt / funding?
Use plausible Assumptions and explicitly flag them as Assumptions. Use simple tables.
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.
- 2d ago Changed · +3 lines 7d38033bace9
- 5d ago First seen · 97 lines · 0 tokens per session scan A 5c1adb3c3ae2
p1-financial-plan is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,088 tokens. 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-31.
Other commands, from other repositories
finops
Estimate and optimize cloud infrastructure costs. Usage - /mindforge:finops [service] [--forecast 6m] [--target-savings 20%].
build-vs-buy
Evaluate build vs buy decision with TCO analysis. Usage: /mindforge:build-vs-buy [capability] [--timeline N months] [--strategic high|low].
mindforge:fintech
Design fintech payment/ledger architecture. Usage: /mindforge:fintech [service] [--domain payments|ledger|kyc] [--compliance pci|sox].
cost-report
Token usage analytics, model routing decisions, and cost optimization recommendations. Usage - /mindforge:cost-report [--window 7d] [--by-model] [--by-task] [--phase N].
costs
Real-time cost tracking for all AI model usage.
scan
Scan AWS account for cost optimization.