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-implementgit 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.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.00841 |
| Opus 5 | $0.00000 | $0.00420 |
| Sonnet 5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
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 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 — 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-skill 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 Manual/WORKITEMS.md §8 for the full guard rationale and the status-verb mapping.
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.
- today 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 today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 841 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
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
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.
CLAUDE
Each subdirectory is one engine verb dispatched by ../cli/cli.ts: / .ts exports a pure handler that resolves the vault, does its work through ../core/ primitives, and returns its own typed report. Commands stay thin — they compose core checks and builders; they do not reimplement them. The canonical output schema is…