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/gate-p7git clone --depth 1 https://github.com/jonase47/ccprWhat 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.01512 |
| Opus 5 | $0.00000 | $0.00756 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
gate-p7 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gate-p7 – Go-Live Gate: Technical Readiness & Business Readiness
Checks whether the system is fully ready for production operation. Last gate before the official go-live status.
No Argument ($ARGUMENTS not applicable)
Gate commands do not accept arguments. They always check the complete current project status.
Pre-Flight
If docs/.gate-preflight-p7.md exists and is less than 10 minutes old, read it as a starting point. Mechanical checks (file existence, sections) are already done – focus on content evaluation.
Constitution Inviolables (mandatory pre-gate, applies to both sub-gates)
If docs/CONSTITUTION.md exists, the preflight report (docs/.gate-preflight-p7.md) includes a section "Constitution Inviolables (Required Read)" with the project's non-negotiable rules.
These Inviolables are mandatory input for both sub-gates (/gate-p7-tech and /gate-p7-business):
- When invoking each sub-gate, pass the Inviolable bullets verbatim in the agent prompt.
- Tech must verify deployment, monitoring, rollback respect the Inviolables (no telemetry-leak, no secret-in-code, A11y-baseline live).
- Business must verify GTM, Pricing, Release-Docs respect the Inviolables (e.g. plain-language privacy statements in marketing copy, A11y mention in store listing).
- Any violation is an "Inviolable breach" — block go-live until resolved or explicitly waived (waiver documented in
GATE_P7.md).
If docs/CONSTITUTION.md is missing on a Full-Track project: stop the gate and require /constitution before go-live.
Flow
1. Technical Go-Live Check
/gate-p7-tech – Checks deployment, monitoring, rollback, and smoke tests.
2. Business Readiness Check
/gate-p7-business – Checks documentation, GTM, KPIs, and mandatory documents.
3. Consolidation (Orchestrator)
Read docs/launch/LAUNCH.md (phase index) first to get the status of all detail files (PREPARE.md, DEPLOYMENT.md, MONITORING.md, RELEASE_DOCS.md, GTM.md). Open detail files only when their row indicates needs-rework or open Critical risks.
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.
- yesterday First seen · 91 lines · 0 tokens per session scan A 431644a8913c
gate-p7 is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,512 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
drift
Post-implementation spec drift check — verify the implementation matches existing OpenSpec specifications.
feature
Orchestrate a complete feature through discovery, spec, implementation, and review.
research
Research a technical or product question.
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
clean-check
Analyze code for cleanliness issues (unused code, comment quality, formatting, naming, complexity). Delegates to the code-cleanliness agent.
build
Mini spec-first development workflow for well-scoped implementation tasks with human in the loop.