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-featuresgit 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.01201 |
| Opus 5 | $0.00000 | $0.00600 |
| Sonnet 5 | $0.00000 | $0.00240 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
p1-features 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p1-features – Feature Definition & MVP Scope Boundary
Defines the feature scope of the project, prioritises using MoSCoW, and clearly defines the MVP scope. The result is FEATURES.md and MVP.md as the binding basis for architecture and planning.
Argument: $ARGUMENTS = [Feature area]
If provided: Focus the feature definition on a specific area (e.g. "authentication", "booking process", "admin area"). If not provided: Read USER_JOURNEYS.md and DISCOVERY.md and develop the complete feature list for the entire project. If any context is missing, ask for the project scope.
Execution
1. Read Context
Read the following files (if available):
- DISCOVERY.md (problem statement, Target Audience, market assessment)
- USER_JOURNEYS.md (personas, user journeys – basis for feature derivation)
- CONCEPT.md (if already available)
2. Delegate to konzeptor Agent (Lead)
Delegate the feature work to the konzeptor agent:
Derive a complete feature catalogue from the user journeys and the problem statement. Context: [Insert DISCOVERY.md and USER_JOURNEYS.md content]. Focus (if provided): $ARGUMENTS
Create:
- Feature Catalogue: All identified features with a short description (1–2 sentences per feature)
- MoSCoW Prioritisation: Assign each feature:
- Must Have: Without this feature the product is worthless
- Should Have: Important, but dispensable in the short term
- Could Have: Nice to have if time permits
- Won't Have (this time): Deliberately excluded from the MVP
- Rationale: Why is a feature a Must Have? Which user journey does it cover?
- Dependencies: Which features build on each other?
3. Delegate to ux-designer Agent (Support)
Delegate the MVP scope definition to the ux-designer agent:
Review the konzeptor's feature catalogue from a UX perspective:
- MVP Scope Recommendation: What is the minimum that enables a genuine user experience?
- Missing Features: What has the konzeptor overlooked that is indispensable for good UX?
- Out-of-Scope Risks: Which excluded features could directly frustrate users?
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 · 95 lines · 0 tokens per session scan A b97ed0346f6d
p1-features 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,201 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
drift
Post-implementation spec drift check — verify the implementation matches existing OpenSpec specifications.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
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.