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/guide)<a href="https://agentmods.dev/commands/jonase47/ccpr/guide"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/guide/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/guide"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/guide.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.01078 |
| Opus 5.5 | $0.00000 | $0.00431 |
| Sonnet 5.5 | $0.00000 | $0.00216 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
guide 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/guide – Project Guide (Status, Command Recommendation, Disambiguation)
Invokes the project-guide agent as the entry point for the current project:
structured status snapshot, prioritised next steps with command/agent
recommendation, and disambiguation for unclear requests.
Argument: $ARGUMENTS = [optional: concrete question / request]
- Without argument: status snapshot + 3 prioritised next steps.
- With argument: disambiguate the request and hand off to the matching domain agent, with 1–2 clarifying questions first if needed.
Execution
- Work-item adoption guard (ADR-0002 §8) —
project-guidehas no Bash access (by design, it's read-only via Read/Grep/Glob/Edit), so if the active phase is P4/P5, the orchestrator resolves this beforehand and passes the result in. Runpython3 ~/.claude/scripts/workitems.py listand explicitly check whether thedocs/workitems/directory exists (e.g.ls docs/workitems/) — both signals are required,listreturns the identical[]for an adopted-but-empty store and a never-adopted project.- Non-empty list → the project uses the structured store. A bare
list --status "Ready"/"In Progress"/"Done"returns PROJECT-WIDE totals across every sprint, not this sprint's. Scope it: read the current sprint number<N>fromdocs/planning/SPRINT.md's frontmattersprint: <N>(or the activedocs/planning/sprint/SPRINT-NN.md'ssprint: NNfield, for the sub-index layout), then runworkitems list --sprint <N>and count status directly among that result. Report the scoped counts as "this sprint" (e.g. "6/10 Done, 2 In Progress, 2 Ready — this sprint"). If SPRINT.md (or the active sprint detail file) carries nosprint:frontmatter yet (a sprint plan predating this convention, or before the project's first/p4-sprintrun under it), scoping isn't possible — report the unscopedlist/--statuscounts but label them explicitly "project-wide", never "this sprint". - Empty list, but
docs/workitems/exists → the store is adopted, just empty right now (or genuinely zero items). Report it as such (e.g. "0 items adopted yet" or "0 in this sprint"), don't fall back to prose. - Empty list and no
docs/workitems/directory → not adopted, still on prose. Derive sprint status from SPRINT.md as before.
- Non-empty list → the project uses the structured store. A bare
- Start the
project-guideagent via the Task tool, passing the resolved item counts (if any, labeled "this sprint" or "project-wide" per the scoping above) as part of its context. - Pass the argument (if present) as the request.
- The guide operates read-only on:
.claude/CLAUDE.mddocs/HANDOVER.mddocs/.session-context.md(if <10 min old)docs/memory/MEMORY.mddocs/BASELINE.md(if Baseline mode is active)- Phase-specific files (SPRINT.md, phase indexes) if needed
~/.claude/docs/NEXT_STEPS_REFERENCE.mdas the phase-sequence reference- Work-item counts prepared by the orchestrator in step 1 (structured-store projects)
- Write permissions for the guide are limited to
docs/memory/project-guide/and its HANDOVER section.
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 761d82e501ed
- 1mo ago First seen · 85 lines · 0 tokens per session scan A 80c72d8615ed
guide is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,078 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-08-31.
Other commands, from other repositories
setup
Interview me and scaffold my personal chief-of-staff system (context file, memory, task list, daily brief).
brief
Produce my morning brief — what's on today, what's slipping, what to prep, one thing worth my attention.
loops
Weekly review — surface everything in-flight and force a ship / block / kill decision on each.
orchestrate
Do this task as an orchestrator. The aim is the same result at a fraction of the cost: in a long session, every token in this conversation is re-read on each later request, while a subagent's reading is discarded when it returns. The plugin's subagents run on Haiku 5.5, about 40× cheaper per token than Opus 5.5.
todo.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
golden-path
The golden path. One command, idea to merged PR. Runs the full pipeline, prd → prp → plan → dev → test → pr, with sensor + eval gates at every stage.