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-polishgit 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-polish)<a href="https://agentmods.dev/commands/jonase47/ccpr/p5-polish"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p5-polish.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.03133 |
| Opus 5 | $0.00000 | $0.01566 |
| Sonnet 5 | $0.00000 | $0.00627 |
| Haiku 4.5 | $0.00000 | $0.00313 |
Grade A, and why
p5-polish 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p5-polish – Sprint Polish: Collect & Resolve Small Carry-Over TODOs
Collects small clean-up TODOs accumulated during the sprint (from /p5-review, /p5-acceptance, /p5-bugfix, TODO/FIXME comments) that do not justify a full story but make the next sprint easier. Triages each item into polish-now, backlog, handover, or drop. Optionally executes polish-now items directly (TDD mini-cycle, one commit per item). Runs between /gate-p5 (Sprint Done) and the next /p4-sprint.
This is not a retrospective – /gate-p5 keeps the 3-point retro. This skill is the cleanup step before the next sprint begins.
Argument: $ARGUMENTS = [mode | POL-ID]
- empty → Hybrid mode (collect + triage + execute small items)
collect-only→ Collect & document only, no code changesexecute→ Execute previously-triagedpolish-nowitems from existing POLISH file<POL-ID>(e.g.POL-03-02) → Work on a single polish item
Preconditions (Hard Block on Violation)
Before doing anything else, verify:
- Gate-p5 passed: Last
gate-p5entry inSPRINT.mdshowsSprint DoneorConditionally Done. If not → stop, recommend/gate-p5first. - CI green: No failing tests or build errors on current commit. If red → stop, recommend
/p5-bugfix. - Working tree clean: No uncommitted changes. If dirty → stop, ask user to commit or stash.
If any precondition fails, write the reason and the recommended next command, then exit. Do not collect, do not execute.
Execution
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 the
backlog-triage items in step 6 below (instead of appending BACKLOG.md prose). []and nodocs/workitems/directory → still on prose. Appendbacklogitems to BACKLOG.md as before. Emit one line: "Tip: runliftto adopt the structured work-item store."[]butdocs/workitems/exists → adopted store, just empty right now. Treat as adopted: use the CLI, not the prose fallback.
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 · 216 lines · 0 tokens per session scan A 9f17791f2827
p5-polish 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 3,133 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
factory-ticket
Implement exactly one already-claimed Linear ticket in the current worktree.
factory-report
Linear status report across configured repos — queue depth, triage backlog, ready-to-dispatch, blocked/held.
get-to-work
Autonomous ops work. Args: [mode] [repeat]. Modes: tasks | opps | full | escalating (default). Repeat: cycle (keep going, default) | once (single pass). Run this before stepping away from an ops repo.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
whats-next
Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".
factory-triage
Find open Linear issues for this repo and triage them toward agent-ready.