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-p6git 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.01584 |
| Opus 5 | $0.00000 | $0.00792 |
| Sonnet 5 | $0.00000 | $0.00317 |
| Haiku 4.5 | $0.00000 | $0.00158 |
Grade A, and why
gate-p6 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 2d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gate-p6 – Release Gate: QA & Security Approval
Checks whether the system is ready for launch. Both QA and Security must explicitly grant approval. No go-live without dual approval.
No Argument ($ARGUMENTS not applicable)
Gate commands accept no arguments. They always check the complete current project status.
Pre-Flight
If docs/.gate-preflight-p6.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-p6.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-p6-qa and /gate-p6-security):
- When invoking each sub-gate, pass the Inviolable bullets verbatim in the agent prompt.
- Both QA and Security must check their evaluation against the Inviolables (e.g. „A11y-Inviolable forces WCAG 2.2 AA verification", „Security-Inviolable forces dependency-audit").
- Any violation is an "Inviolable breach" — surface it explicitly in the sub-gate verdict and treat it as a No-Go signal for release.
If docs/CONSTITUTION.md is missing on a Full-Track project: stop the gate and recommend /constitution before proceeding (release without Constitution check is not advisable in Full-Track).
Flow
1. QA Approval
/gate-p6-qa – Evaluates all QA-relevant points (tests, accessibility, performance, bugs) and grants QA approval.
2. Security Approval
/gate-p6-security – Evaluates all security-relevant points (audit, pentest, DSGVO) and grants Security approval.
3. Consolidation (Orchestrator)
Read docs/quality/QA.md (phase index) first to get the status of all sub-indexes (A11Y.md, AUDIT.md, FUNCTIONAL.md, PENTEST.md) and direct detail files (EXPLORATORY.md, BUGFIX.md). Open the sub-indexes only when their status 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.
- 2d ago First seen · 91 lines · 0 tokens per session scan A 2b1043b68456
gate-p6 is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,584 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
factory-ship
Release — open a develop → master PR, wait for CI, merge, verify the deploy.
release
Cut a release with synchronized versions, notes, commit, tag, push, GitHub Release, and npm publication gates.
release
Bump version and cut a release.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.