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/user-storiesgit 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/user-stories)<a href="https://agentmods.dev/commands/jonase47/ccpr/user-stories"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/user-stories.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.1 | $0.00000 | $0.01437 |
| Opus 5 | $0.00000 | $0.00718 |
| Sonnet 5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade A, and why
user-stories 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/user-stories – Create or elaborate user stories
Purpose
This command creates detailed user stories – either derived from an existing epic, roadmap, or concept, or standalone from a free description. Each story contains acceptance criteria, priority, dependencies, and a definition of done.
Execution
Step 1 – Load context
Check whether the user named a source file:
- Epic file → read from
docs/epics/ - Roadmap → read from
docs/roadmaps/ - Concept file → read from
docs/concepts/ - No file → standalone, work with the description from the prompt
If user stories are already present in the epic (raw drafts from /epic):
use these as the starting basis and elaborate them, do not reinvent.
If no source file and no sufficient description is available:
"Describe briefly what should be implemented, or give me an epic/concept file."
Step 2 – Clarify scope & focus
If derived from an epic and multiple raw stories are present:
"I see [X] stories in the epic. Elaborate all of them or prioritize specific ones?"
If standalone:
"For which user group(s) should stories be created?"
Step 3 – Parallel elaboration by sub-agents
Distribute the stories across parallel sub-agents using the Task tool.
Rule of thumb: up to 3 stories per agent; for many stories use multiple agents.
Mark ambiguities as [UNCLEAR: ...].
Each sub-agent elaborates their assigned stories according to the following schema:
Per user story:
- Assign story title & ID (format:
E-{NN}-S{NN}, see/p4-backlogticket ID schema) - Check/sharpen story formulation: "As a [role] I want [action] so that [benefit]."
- Formulate acceptance criteria (concrete & testable, at least 2-3)
- Justify priority: High / Medium / Low
- Identify dependencies (other stories, epics, external factors)
- Formulate definition of done for this story
- Rough effort estimate: XS / S / M / L / XL
Step 4 – Interactive clarification round
Collect all [UNCLEAR: ...] markers from all sub-agents,
prioritize by impact on the stories and ask bundled:
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 · 181 lines · 0 tokens per session scan A d7ebe857a1fb
user-stories 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,437 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-09-03.
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].
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.