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/p0-marketgit 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/p0-market)<a href="https://agentmods.dev/commands/jonase47/ccpr/p0-market"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p0-market.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.01102 |
| Opus 5 | $0.00000 | $0.00551 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
p0-market 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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p0-market – Market Assessment & Competition Overview
Delivers a first market assessment: Is there demand? Who are the competitors? Is the idea roughly viable economically? The result is an overview needed for the Go/No-Go Decision at Gate 0.
Argument: $ARGUMENTS = [Industry / market segment]
If provided: Use as the focus for the market research (e.g. "E-Health", "B2B-SaaS", "local trades"). If not provided: Read DISCOVERY.md (problem statement and Target Audience) and derive the industry from it. If DISCOVERY.md is also missing, ask for the market segment.
Execution
1. Read Context
Read docs/discovery/DISCOVERY.md (phase index) and docs/discovery/PROBLEM.md (detail file from /p0-problem) to understand the problem statement and Target Audience. This information is essential for a meaningful market assessment.
2. Delegate to konzeptor Agent (Lead)
Delegate the structuring and evaluation to the konzeptor agent:
Create a first market assessment for the segment: $ARGUMENTS Context from PROBLEM.md: [Insert problem statement, Target Audience]
Work out:
- Market Size (Rough estimate: How many potential customers/users are there?)
- Demand Indicators (Are there signs of genuine need? Search volume, forums, existing solutions?)
- Competition Overview (3–5 direct or indirect competitors with a brief assessment)
- Differentiation Potential (Where could a new solution do better?)
- First Economic Assessment (Is there a business here? Rough willingness to pay?)
3. Delegate to business-analyst Agent (Support)
Delegate the economic assessment in parallel or afterwards to the business-analyst agent:
Supplement the konzeptor's market assessment with:
- Rough market size in euros (TAM/SAM if possible, otherwise qualitative estimate)
- Typical willingness to pay in this segment
- First assessment: Is this economically worthwhile – why yes/no?
4. Write Detail File
Write the result to docs/discovery/MARKET.md (overwrite if it exists). Start with this YAML frontmatter:
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.
- yesterday Changed · +3 lines 546aa76f8fb2
- 4d ago First seen · 82 lines · 0 tokens per session scan A 67edf897ce68
p0-market 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,102 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.
wiki-tune
Tune wiki schema and conventions interactively.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
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.