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/p5-implement)<a href="https://agentmods.dev/commands/jonase47/ccpr/p5-implement"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p5-implement/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/p5-implement"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p5-implement.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.00853 |
| Opus 5.5 | $0.00000 | $0.00341 |
| Sonnet 5.5 | $0.00000 | $0.00171 |
| Haiku 4.5 | $0.00000 | $0.00085 |
Grade A, and why
p5-implement 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p5-implement – Implement Feature (TDD Cycle)
Implements a feature in the TDD cycle: Red → Green → Refactor. Each phase is its own sub-command with a focused agent call.
Argument: $ARGUMENTS = [Feature name/Story ID]
If provided: Implement the named feature. If not provided: resolve the next story via the work-item adoption guard below (falls back to reading SPRINT.md and asking, if the project is still on prose).
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 next story viaworkitems list --status "Ready", pick the first item in the returned array, ask for confirmation. $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 claiming it.- Claim + start:
workitems claim <id> --owner <who>thenworkitems set-status <id> "In Progress". Resolve<who>fromgit config user.name; if that is unset, ask the user.
- No
[]and nodocs/workitems/directory → still on prose. Read SPRINT.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 docs/adr/ADR-0002-workitem-backend-contract.md for the adoption-guard rationale and the status vocabulary.
Flow
1. RED – Write failing tests
/p5-impl-red $ARGUMENTS – Writes unit tests before production code exists. Tests must fail.
2. GREEN – Minimal production code
/p5-impl-green $ARGUMENTS – Writes the minimal code that makes the tests green.
3. REFACTOR – Clean up code
/p5-impl-refactor $ARGUMENTS – Improves code quality without changing behavior.
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 02f7cbec50e1
- 2mo ago Changed c7a741865f5c
- 2mo ago Changed 453076ce063f
- 2mo ago First seen · 64 lines · 0 tokens per session scan A 0041ac60b6eb
p5-implement 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 853 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.
p5-implement compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| p5-implementjonase47/ccpr | Command | 1 | 1mo ago | MIT | A | 0 | Claude Code |
| cpp-testaffaan-m/ECC | Command | 298k | 5d ago | MIT | A | 25 | Claude Code |
| go-testaffaan-m/ECC | Command | 298k | 5d ago | MIT | A | 8 | Claude Code, OpenCode |
| statsAR6420/Hail_Hydra | Command | 51 | 5d ago | MIT | A | 29 | Claude Code |
| ralphjoaquimscosta/arkhe-claude-plugins | Command | 22 | 22d ago | MIT | A | 10 | Claude Code |
| debugjoaquimscosta/arkhe-claude-plugins | Command | 22 | 22d ago | MIT | A | 48 | Claude Code |
| stitch-generatejoaquimscosta/arkhe-claude-plugins | Command | 22 | 22d ago | MIT | A | 16 | Claude Code |