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/p2-market-validationgit 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/p2-market-validation)<a href="https://agentmods.dev/commands/jonase47/ccpr/p2-market-validation"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p2-market-validation.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.00000 | $0.01366 |
| Opus 5 | $0.00000 | $0.00683 |
| Sonnet 5 | $0.00000 | $0.00273 |
| Haiku 4.5 | $0.00000 | $0.00137 |
Grade A, and why
p2-market-validation 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 today.
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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p2-market-validation – Validate Market, Pricing & Demand Assumptions
Checks critical market, pricing, and demand Assumptions from the Assumptions register using concrete research, data, and competitive analyses. The result is confirmed or refuted Assumptions as the basis for informed Concept decisions.
Argument: $ARGUMENTS = [Specific assumption or assumption ID from ASSUMPTIONS.md]
If provided: Validate the named assumption or assumption ID specifically (e.g. "A-03", "B2B willingness to pay").
If not provided: Read ASSUMPTIONS.md and validate the highest-priority market and financial Assumptions. If ASSUMPTIONS.md is missing in an autonomous pipeline run, infer the top-3 market/financial assumptions from CONCEPT.md / FEATURES.md, log this fallback in HANDOVER.md ("validated without ASSUMPTIONS.md, basis = MVP scope"), and continue. Only halt and recommend running /p2-assumptions first when running interactively.
Execution
1. Read Context
Read the following files (if available):
- ASSUMPTIONS.md (Assumptions register – which Assumptions should be validated?)
- DISCOVERY.md (market assessment from Phase 0 as starting point)
- BUSINESS_MODEL.md / FINANCIAL_PLAN.md (pricing Assumptions)
2. Delegate to business-analyst Agent (Lead)
Delegate the market validation to the business-analyst agent:
Validate the following assumption(s): $ARGUMENTS Context from ASSUMPTIONS.md and DISCOVERY.md: [Insert relevant Assumptions and market context]
For each assumption to be validated, conduct:
A. Demand Validation
- Are there measurable demand signals? (search volume, forums, communities, waitlists)
- Are comparable products/services successful in the market?
- Back up with concrete data sources or examples
B. Pricing Validation
- What do customers pay for comparable solutions? (competitor pricing research)
- Is there public data on willingness to pay in this segment?
- Is the own pricing approach from BUSINESS_MODEL.md in line with the market?
C. Competitive Validation
- Have competitors changed since DISCOVERY.md?
- Are there new market participants or product changes?
- Differentiation potential still valid?
D. Result per Assumption
- ✅ Confirmed: Assumption holds, evidence available
- ⚠️ Partially confirmed: Assumption must be adjusted
- ❌ Refuted: Assumption is wrong – consequence for the Concept?
- ❓ Not validatable with available means: What approach is recommended?
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.
- today Changed · +3 lines d939a0196962
- 4d ago First seen · 108 lines · 0 tokens per session scan A 186f1f1e0cee
p2-market-validation 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,366 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
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
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…