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-impl-green)<a href="https://agentmods.dev/commands/jonase47/ccpr/p5-impl-green"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p5-impl-green/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-impl-green"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p5-impl-green.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.00529 |
| Opus 5.5 | $0.00000 | $0.00212 |
| Sonnet 5.5 | $0.00000 | $0.00106 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
p5-impl-green 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p5-impl-green – Minimal Code for Green Tests (GREEN)
Writes the minimal production code that makes the existing tests green. No over-engineering.
Argument: $ARGUMENTS = [Feature name/Story ID]
If provided: Implement code for the named feature. If not provided: Ask which feature should be implemented.
Prerequisites
/p5-impl-redcompleted (failing tests exist)
Agent
- Type: senior-developer
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads beforehand and provides inline:
- From tests/: the failing test files (complete)
- From ARCHITECTURE.md: affected modules, file structure (relevant section only)
- From SECURITY.md: security checklist (affected points only)
Prompt Template
Goal: Write minimal production code that makes all tests green for Story [ID]: [Title]
Failing Tests: [inline from tests/]
Architecture Guidelines: [inline from ARCHITECTURE.md]
Output Format:
- Production code file(s) in the src/ directory
- At the end: summary of which files were created/changed
Constraints:
- ONLY as much code as needed to make tests green
- No over-engineering, no anticipatory abstractions
- Follow security checklist from SECURITY.md
- All tests must be green after implementation
Orchestrator Checkpoint
- All tests green?
- No unnecessary code written?
- Security checklist followed?
- Commit after GREEN:
feat: [Story-ID] [Description]
Output
- Production code file(s) in src/
Handover Epilog
Update docs/HANDOVER.md:
- What was created/changed
- Open decisions → the
## Open Decisionstable; a finding outside this command's scope goes to the## Open Pointsinbox instead - Next Steps (according to
~/.claude/docs/NEXT_STEPS_REFERENCE.md)
Recommend 1-3 sensible next commands to the user:
- Read
docs/HANDOVER.mdfor the current project status - Consult
~/.claude/docs/NEXT_STEPS_REFERENCE.mdfor allowed transitions - Only suggest commands that match the current phase/sub-command status
- If the current phase appears complete: recommend the gate
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 44269e021aef
- 1mo ago First seen · 65 lines · 0 tokens per session scan A 136e74da4ae5
p5-impl-green is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 529 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
cpp-test
Enforce TDD workflow for C++. Write GoogleTest tests first, then implement. Verify coverage with gcov/lcov.
go-test
Go TDD workflow with table-driven tests.
rust-test
Rust TDD workflow with unit and property tests.
tdd
A command for test-driven development, a method where you write a failing test first, then code to pass it, and finally improve the code.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
test
Design or run focused test validation for a task, bug, or diff.