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-business-modelgit 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-business-model)<a href="https://agentmods.dev/commands/jonase47/ccpr/p1-business-model"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p1-business-model.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.01181 |
| Opus 5 | $0.00000 | $0.00590 |
| Sonnet 5 | $0.00000 | $0.00236 |
| Haiku 4.5 | $0.00000 | $0.00118 |
Grade A, and why
p1-business-model 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p1-business-model – Business Model Canvas & Value Proposition
Develops the Business Model with Business Model Canvas, sharpens the value proposition, and defines a first pricing approach. The result is BUSINESS_MODEL.md as the economic foundation of the project.
Argument: $ARGUMENTS = [Business Model type, e.g. "SaaS", "service", "marketplace"]
If provided: Focus the development on the specified Business Model type and its typical mechanics. If not provided: Read DISCOVERY.md, FEATURES.md and MVP.md and derive the most sensible Business Model type. If any context is missing, ask for the desired model.
Execution
1. Read Context
Read the following files (if available):
- DISCOVERY.md (problem statement, Target Audience, market assessment incl. willingness to pay)
- FEATURES.md / MVP.md (What is being built?)
- USER_JOURNEYS.md (Who are the users?)
2. Delegate to konzeptor Agent (Lead)
Delegate the conceptual development to the konzeptor agent:
Develop the Business Model for this project. Business Model type (if provided): $ARGUMENTS Context: [Insert problem statement, Target Audience, MVP scope]
Create a complete Business Model Canvas with all 9 building blocks:
- Customer Segments: Who are our most important customers?
- Value Propositions: What value do we create for each segment?
- Channels: How do we reach customers and deliver the value?
- Customer Relationships: What relationships do we have with customers?
- Revenue Streams: What do customers pay for? How much?
- Key Resources: What do we need to operate the model?
- Key Activities: What must we do?
- Key Partnerships: Who do we depend on?
- Cost Structure: What are the biggest cost drivers?
Also add:
- Value Proposition Statement (1 concise sentence: For [Target Audience] who have [problem], [product] offers [solution], unlike [alternative])
- Pricing Approach: Concrete recommendation with rationale (e.g. freemium from X€/month, one-time payment Y€, etc.)
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 22a8b894e085
- 5d ago First seen · 93 lines · 0 tokens per session scan A 797ad99d9128
p1-business-model 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,181 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
sdd-implement
Execute a task list in dependency order, tests before implementation for each task, halting on any non-parallel failure instead of pressing ahead.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
pseo-init
Use when: kullanıcı "yeni proje", "init", "proje kur", "yeni domain ekle", "scaffold" gibi ifadeler kullanır ya da /pseo-init çağırırsa. Also use when: portföye yeni bir SEO projesi alındı, projects/{slug}/ klasörü ve project.config.json dosyasının schemaya uygun ilk hâli üretilecek; brief'te slug + domain + market…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.
CLAUDE
Each subdirectory is one engine verb dispatched by ../cli/cli.ts: / .ts exports a pure handler that resolves the vault, does its work through ../core/ primitives, and returns its own typed report. Commands stay thin — they compose core checks and builders; they do not reimplement them. The canonical output schema is…