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/gate-p3)<a href="https://agentmods.dev/commands/jonase47/ccpr/gate-p3"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/gate-p3/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/gate-p3"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/gate-p3.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.02398 |
| Opus 5.5 | $0.00000 | $0.00959 |
| Sonnet 5.5 | $0.00000 | $0.00480 |
| Haiku 4.5 | $0.00000 | $0.00240 |
Grade A, and why
gate-p3 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gate-p3 – Quality Gate 3: Architecture & Design → Planning
Checks whether all architecture and design decisions are completely documented and robust before transitioning into the planning and implementation phase. No argument – this gate always checks the complete checklist.
No Argument ($ARGUMENTS not applicable)
Gate commands accept no arguments. They always check the complete current project status.
Execution
1. Read Preflight Report
Read docs/.gate-preflight-p3.md as the primary information source. This report contains:
- Artifact existence and required sections (mechanically checked)
- Content check (regex-based: diagrams, data flows, trade-offs, ERD, STRIDE, CI/CD, coverage)
- Document summaries (via Ollama, if available)
If the preflight report does not exist or is older than 10 minutes, read the architecture documents directly instead — always start with the phase index, then the sub-indexes, then detail files only as needed:
docs/architecture/ARCHITECTURE.md(phase index) — gives you the detail-file table, key decisions, open risks, gate notes.- The three sub-indexes called out in the phase index:
docs/architecture/SECURITY.md(sub-index for/p3-sec-*)docs/architecture/UX_CONCEPT.md(sub-index for/p3-ux-*)docs/architecture/INFRA.md(sub-index for/p3-infra-*)
- Direct phase-level detail files only when content checks demand them:
COMPONENTS.md,TECH_STACK.md,NFR.md,DATA_MODEL.md,API_SPEC.md,COST_ESTIMATION.md,ADR/*.md
- Sub-index detail files only when the relevant sub-index flags an open question:
- Security:
THREATS.md,AUTH.md,DATA_SECURITY.md,API_SECURITY.md,CHECKLIST.md - UX:
NAVIGATION.md,WIREFRAMES.md,DARKMODE.md,A11Y.md - Infra:
HOSTING.md,CICD.md,MONITORING.md,TESTSTRATEGY.md
- Security:
1a. Constitution Inviolables (mandatory pre-gate)
If docs/CONSTITUTION.md exists, the preflight report (docs/.gate-preflight-p3.md) includes a section "Constitution Inviolables (Required Read)" with the project's non-negotiable rules.
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 c7bf109ca541
- 1mo ago Changed · +3 lines 070830711de8
- 1mo ago First seen · 153 lines · 0 tokens per session scan A 9ecc580b7b6f
gate-p3 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 2,398 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
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
map
View, rebuild, or query the codebase dependency map.
design-intent
Guided UI/visual development with structured exploration, architecture design, and quality review.
ralph
Ralph autonomous development loop with fresh context per iteration.
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
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.