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.
git 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-journeys)<a href="https://agentmods.dev/commands/jonase47/ccpr/p1-journeys"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p1-journeys/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/jonase47/ccpr/p1-journeys"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p1-journeys.svg" alt="Reviewed on agentmods" width="80" 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.01133 |
| Opus 5.5 | $0.00000 | $0.00453 |
| Sonnet 5.5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
p1-journeys 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 1mo 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p1-journeys – Personas & User Journeys
Develops detailed personas, user journeys, and usage scenarios based on the Discovery results. These artefacts form the user foundation for all further conception decisions.
Argument: $ARGUMENTS = [Persona / scenario focus]
If provided: Focus the work on a specific user type or scenario (e.g. "first-time user", "power user", "mobile usage"). If not provided: Read DISCOVERY.md and CONCEPT.md (if available) and develop personas and journeys for all relevant Target Audience segments. If any context is missing, ask for the focus.
Execution
1. Read Context
Read the following files (if available):
- DISCOVERY.md (problem statement, Target Audience sketch)
- CONCEPT.md (if already available)
- FEATURES.md (if already available)
2. Delegate to konzeptor Agent (Lead)
Delegate the content development to the konzeptor agent:
Develop personas and user journeys for the project. Context from DISCOVERY.md: [Insert problem statement, Target Audience]. Focus (if provided): $ARGUMENTS
Create:
- Personas (2–4): For each persona: name, age, role/occupation, goals, frustrations, technical affinity, typical context of use
- User Journeys (at least 3): Per journey: persona, starting situation, steps (actions + thoughts + feelings), touchpoints, pain points, success criterion
- Scenarios: Concrete usage scenarios covering edge cases and critical moments
- Open Questions: What still needs to be validated with real users?
3. Delegate to ux-designer Agent (Support)
Delegate the UX perspective to the ux-designer agent:
Supplement the konzeptor's personas and user journeys with:
- Information Architecture Implications: What do the journeys mean for the structure of the application?
- Critical Interaction Points: Where are drop-offs or frustration likely?
- Accessibility Notes: Which personas have special requirements (visual impairment, motor limitations)?
- Prioritisation: Which journey is the most important (critical path)?
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.
- 1mo ago Changed 49800f92acc0
- 1mo ago Changed 65b2dbf40be1
- 1mo ago Changed · +3 lines 3d5a2912eb0d
- 2mo ago First seen · 84 lines · 0 tokens per session scan A 4e48da22647a
p1-journeys is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,133 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
design-intent
Guided UI/visual development with structured exploration, architecture design, and quality review.
prompt
Generate Google Stitch-ready prompts from briefs or spec files using the authoring skill.
stitch-generate
Full Stitch pipeline — author prompts, generate screens via MCP, fetch images and code.
prototype
Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery.
stitch-setup
Guided setup and verification of Stitch MCP server connection.
ccc-theme
List, preview or switch the Commander terminal color theme (Claude, OLED Black, Matrix, or a random palette) used by hooks and terminal art. Use when the user asks to change the theme, colors or skin.