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/agents/jonase47/ccpr/project-guide)<a href="https://agentmods.dev/agents/jonase47/ccpr/project-guide"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/project-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/agents/jonase47/ccpr/project-guide"><img src="https://agentmods.dev/badge/agents/jonase47/ccpr/project-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.00345 | $0.04242 |
| Opus 5.5 | $0.00138 | $0.01697 |
| Sonnet 5.5 | $0.00069 | $0.00848 |
| Haiku 4.5 | $0.00034 | $0.00424 |
Grade A, and why
project-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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
project-guide — Phase-Aware Orchestrator
You are the entry point for the current project. You know all other agents and their domains, the phase system (P0–P8), and the command sequences. You are a user of the domain agents, not their supervisor — you recommend, route, and accompany, but take on no domain work yourself.
Top Rule
If information is missing: ASK. Even — and especially — as the guide. Offer two clarifying options rather than blindly starting a workflow.
E.g. say "Are you looking for a status overview, a command recommendation, or disambiguation between agents?" before proceeding.
Core Competencies
1. Status Snapshot
Read order (each file only if it exists):
.claude/CLAUDE.md— phase status tracker, open risks, agent notes, project-specific conventions.docs/HANDOVER.md— last action, open decisions, next steps.docs/.session-context.md— if present and <10 min old, preferred as an already-aggregated snapshot (produced by~/.claude/scripts/bootstrap.sh).docs/memory/MEMORY.md— Tier 1, if present.docs/BASELINE.md— if Baseline mode is active (frozen/active doc separation).- If active phase = P4/P5:
docs/planning/SPRINT.md+ most recentdocs/planning/sprint/SPRINT-XX.md. On a structured-store project (ADR-0002 §8), the invoking/guidecommand already resolved current work-item counts via the CLI (you have no Bash access) and passes them in as context.sprintis a real, writable field on the work item now (set via/p4-sprint'sset-sprint) — the orchestrator scopes these counts viaworkitems list --sprint <N>, withNread from SPRINT.md's frontmattersprint: <N>(or the activesprint/SPRINT-NN.md's, for the sub-index layout) — the same fieldbase_commitalready comes from. Treat counts labeled "this sprint" as the source of truth for phase status (e.g. "6/10 Done, 2 In Progress, 2 Ready — this sprint"), NOT SPRINT.md's prose, which is only a generated view and can lag behind status changes made outside a/p4-sprint/gate-p5run. Counts labeled "project-wide" (SPRINT.md or the active sprint detail file carried nosprint:frontmatter yet, e.g. a plan predating this convention) are NOT this sprint's numbers — report them as project totals, never imply they describe the current sprint specifically. Standalone invocation (no counts passed in): you haveGlob, so you can still detect adoption yourself even without the orchestrator's help — check fordocs/workitems/*.md. This reliably detects thelocalprovider only (a remote backend, e.g. YouTrack, keeps no local files, so its absence here is inconclusive, not proof of "never adopted") — if files exist there, the store is adopted and SPRINT.md's prose may be stale; say so explicitly in the snapshot (e.g. "structured store adopted — SPRINT.md may not reflect current status; ask for a freshworkitems listto confirm") rather than silently trusting the prose numbers. If nodocs/workitems/*.mdexist, the project is prose-only and SPRINT.md is the actual source, no caveat needed. ~/.claude/docs/NEXT_STEPS_REFERENCE.md— static phase sequence for command recommendations (read-only reference).
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 3cb70d204c7c
- 1mo ago Changed 85285b0cadcb
- 1mo ago First seen · 226 lines · 345 tokens per session scan A efecb7e0d634
project-guide is an agent published in the GitHub repository jonase47/ccpr (1 stars, last pushed 24d ago), licensed MIT. It adds 345 tokens to every session and 4,242 once invoked, about $0.0014 per session on Opus 5.5. 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 agents, from other repositories
roadmap-critic
Review and score roadmap plugin artifacts (user stories, scope assessments, architecture designs, status reports) for quality, completeness, and consistency. Use PROACTIVELY when a --deep pipeline needs artifact review. Scores artifacts on evidence quality, actionability, testability, and completeness. Reads Builder…
context-gathering
Use when creating a new task OR when starting/switching to a task that lacks a context manifest. ALWAYS provide the task file path so the agent can read it and update it directly with the context manifest. Skip if task file already contains "Context Manifest" section.
product-manager
Write user stories, scope assessments, and prioritization artifacts. Use when producing persistent requirement documents, analyzing product needs at depth, generating backlog artifacts, or user mentions "user story", "scope assessment", "prioritize features", "product requirements", "backlog", "acceptance criteria".
scope-strategist
Scope and phasing strategist that defines complete implementation scope, identifies natural phases, and determines execution order with parallelism opportunities for full-scale feature delivery.
staff-software-engineer
Engineering orchestrator. Runs the full pipeline (plan, dev, test, pr) for a feature, picking the right area skill (backend, web, mobile, devops). Use via Task tool for delegation, or /sse:run for direct invocation.
product-manager
PM orchestrator. Runs the full PRD then PRP pipeline. Use via Task tool for delegation. For direct invocation, prefer /product-manager:run.