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/p5-acceptancegit 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/p5-acceptance)<a href="https://agentmods.dev/commands/jonase47/ccpr/p5-acceptance"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p5-acceptance.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.01382 |
| Opus 5 | $0.00000 | $0.00691 |
| Sonnet 5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
p5-acceptance 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 today.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p5-acceptance – Acceptance Tests
Tests an implemented feature against its requirements from a user perspective: are all acceptance criteria met? Are edge cases handled correctly? The result is test findings that determine whether the feature counts as "Done".
Argument: $ARGUMENTS = [Feature name/Story ID]
If provided: Test the named feature against its acceptance criteria. If not provided: resolve the story via the work-item adoption guard below (falls back to reading SPRINT.md and asking, if the project is still on prose). If context is missing, ask for the feature name or story ID.
0. Work-item adoption guard (ADR-0002 §8)
Run python3 ~/.claude/scripts/workitems.py list.
- Non-empty array → the project uses the structured store. Use the CLI for all item state below:
- No
$ARGUMENTS: resolve the story viaworkitems list --status "Waiting for Approval", pick the first item in the returned array, ask for confirmation. Acceptance criteria come fromworkitems get <id>(descriptionfield) instead of BACKLOG.md prose. $ARGUMENTSprovided: resolve<id>by matching$ARGUMENTSagainst a story's title, or directly if it looks like aWork-Itemid (WI-NNNN) from BACKLOG.md/SPRINT.md, then confirm the resolved item with the user before proceeding.
- No
[]and nodocs/workitems/directory → still on prose. Read SPRINT.md/BACKLOG.md to find/ask which story is next, as before. Emit one line: "Tip: runliftto adopt the structured work-item store."[]butdocs/workitems/exists → adopted store, just empty right now (e.g. between sprints). Treat as adopted: use the CLI, not the prose fallback.
See Manual/WORKITEMS.md §8 for the full guard rationale and the status-verb mapping.
Execution
1. Read Context
Read the following files (if available):
- BACKLOG.md (acceptance criteria of the story – this is the test standard)
- SPRINT.md (sprint context and Definition of Done)
- USER_JOURNEYS.md (persona and journey context for realistic test scenarios)
- UX_CONCEPT.md (UI specifications for visual checks)
- TEST_STRATEGY.md (test levels and methods)
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.
- today First seen · 120 lines · 0 tokens per session scan A 257a83ff96e2
p5-acceptance 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,382 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
ui-snapshot.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
plan-spec
仅在人工明确安排 UI 自动化时，根据任务、产品规则或原型生成独立行为 Spec.
test-run
Run E2E tests with qa-use CLI.
record
Record the browser while validating a flow, then judge it against a rubric.
maestro-selectors-instructions
Guide to using Maestro selectors for targeting UI elements in tests.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].