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-p7-tech)<a href="https://agentmods.dev/commands/jonase47/ccpr/gate-p7-tech"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/gate-p7-tech/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-p7-tech"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/gate-p7-tech.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.00903 |
| Opus 5.5 | $0.00000 | $0.00361 |
| Sonnet 5.5 | $0.00000 | $0.00181 |
| Haiku 4.5 | $0.00000 | $0.00090 |
Grade A, and why
gate-p7-tech 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gate-p7-tech – Technical Go-Live Check
Checks technical go-live readiness: deployment, monitoring, rollback, smoke tests.
Argument: $ARGUMENTS = not applicable
Gate commands do not accept arguments.
Prerequisites
docs/launch/LAUNCH.md(phase index) existsdocs/launch/PREPARE.md(pre-launch checklist) with frontmatterstatus: activedocs/launch/DEPLOYMENT.md(deployment log) with frontmatterstatus: activedocs/launch/MONITORING.md(monitoring & runbook) with frontmatterstatus: activedocs/quality/GATE_P6.md(P6 approval) exists
Agent
- Type: devops
- Model: sonnet
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.
Context (Orchestrator prepares)
Read the phase index first, then load detail files only when their status row signals an open issue:
- From
docs/launch/LAUNCH.md: status, key decisions, open risks (entry point) - From
docs/launch/DEPLOYMENT.md: deployment status, smoke test results - From
docs/launch/MONITORING.md: monitoring status, rollback plan, alerting rules - From
docs/launch/PREPARE.md: any unfinished checklist items - From
docs/quality/GATE_P6.md: QA and security approval status
Prompt Template
Goal: Technical go-live check for Gate P7.
Technical Reports: [inline summaries]
Output Format:
Checklist (max. 6 items): | # | Check | Status | Reason | Status: Fulfilled / Partially / Not fulfilled
Technical go-live approval:
- Approval / Conditional approval / No approval
- Reason (2-3 sentences)
- Conditions (if conditional, as numbered list)
Constraints:
- ONLY technical check, NO business evaluation
- Focus: deployment, monitoring, rollback, smoke tests
- No approval if deployment failed or no rollback plan exists
Orchestrator Checkpoint
- Deployment status checked?
- Rollback plan present and tested?
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 861de645c690
- 1mo ago Changed · +3 lines fb24d0cba635
- 1mo ago First seen · 78 lines · 0 tokens per session scan A 59565ee4c85a
gate-p7-tech 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 903 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.