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-assumptionsgit clone --depth 1 https://github.com/jonase47/ccprWhat 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.01223 |
| Opus 5 | $0.00000 | $0.00611 |
| Sonnet 5 | $0.00000 | $0.00245 |
| Haiku 4.5 | $0.00000 | $0.00122 |
Grade A, and why
p2-assumptions 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p2-assumptions – Identify & Prioritise Critical Assumptions
Systematically lists all critical Assumptions from the conception phase and prioritises them by risk and validatability. The result is an Assumptions register that serves as the working basis for all further validation steps.
Argument: $ARGUMENTS = [Focus area, e.g. "market", "technology", "regulatory"]
If provided: Focus the Assumptions register on the specified area. If not provided: Read all conception documents and create a complete, cross-area Assumptions register. If any context is missing, ask for the project background.
Execution
1. Read Context
Read the following files (if available):
- CONCEPT.md (consolidated Concept)
- FEATURES.md / MVP.md
- BUSINESS_MODEL.md / FINANCIAL_PLAN.md
- DSGVO_INITIAL_ASSESSMENT.md
- DISCOVERY.md
2. Delegate to konzeptor Agent (Lead)
Delegate the Assumptions analysis to the konzeptor agent:
Read all conception documents and extract all Assumptions from them – everything that was treated as fact but has not yet been proven. Focus (if provided): $ARGUMENTS
Create an Assumptions Register with the following structure per assumption:
ID Assumption Area Consequence if wrong Validatability Priority
- Area: Market / Technology / Regulatory / User / Finance
- Consequence if wrong: What happens to the project if this assumption is not correct? (Low / High / K.O.)
- Validatability: How difficult is this assumption to validate? (Easy / Medium / Hard)
- Priority: Combination of consequence and validatability → Which Assumptions must be checked first?
Explicitly mark the Top 3 most critical Assumptions – these must be validated in Phase 2 without fail.
Also suggest a concrete validation method for each assumption:
- Desk research / market research
- Technical Proof of Concept
- User conversations / interviews
- Numbers / data / statistics
- Regulatory inquiry / lawyer
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 First seen · 98 lines · 0 tokens per session scan A 438d217d24f8
p2-assumptions is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,223 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
research
Research a technical or product question.
status
Show Hydra framework status — installed agents, version, config, and update availability.
help
Show everything the Obsidian Knowledge Agent can do, with every command and an example.
clean-check
Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.