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/p6-bugfix)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-bugfix"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-bugfix/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/p6-bugfix"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-bugfix.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.01358 |
| Opus 5.5 | $0.00000 | $0.00543 |
| Sonnet 5.5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
p6-bugfix 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-bugfix – Fix QA Findings
Fixes bugs and vulnerabilities found during the QA phase (functional tests, exploratory tests, accessibility check, security audit, pentest). Each fix is secured by a regression test.
Argument: $ARGUMENTS = [bug description/finding ID from a QA protocol]
If provided: Fix the specified finding or the bug with the given ID. If not provided: Read all QA protocols (TESTPROTOCOL_*.md, SECURITY_AUDIT_REPORT.md, PENTEST_REPORT.md) and ask which findings should be fixed with priority. Do not make assumptions about the order.
Execution
1. Read Context
Read the following files (if present) to understand the finding context:
- TESTPROTOCOL_FUNCTIONAL.md (functional bugs)
- TESTPROTOCOL_EXPLORATORY.md (exploratory findings)
- TESTPROTOCOL_A11Y.md (accessibility findings)
- SECURITY_AUDIT_REPORT.md (security audit findings)
- PENTEST_REPORT.md (pentest findings)
- Relevant source code files (derive from finding description)
2. Delegation to Debugger Agent (Lead)
Delegate the root cause analysis to the debugger agent:
Analyse the following finding from the QA phase: $ARGUMENTS Finding details: [Insert description, affected component, severity from QA protocol]
A. Root Cause Analysis
- Where exactly is the cause in the code? (file, function, line)
- Why does the problem occur? (logic error, missing validation, insecure implementation)
- Is the finding present only at this location or at multiple places in the code?
- Are there related findings that share the same cause?
B. Security Findings (for security audit / pentest) For security findings, additionally:
- Which attack scenario does the fix prevent?
- Are there mitigation measures that take immediate effect until the clean fix is deployed?
- Does the Security Architecture in SECURITY.md need to be updated?
C. Accessibility Findings For accessibility findings, additionally:
- Which WCAG criterion does the fix satisfy?
- Which user group benefits from the fix?
D. Fix Strategy
- Minimal, correct fix – what needs to be changed?
- Risk: Does the fix affect other areas?
- Which regression test needs to be written?
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 44d566818eeb
- 1mo ago First seen · 112 lines · 0 tokens per session scan A 415eebafbd44
p6-bugfix is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,358 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-09-03.
Other commands, from other repositories
verify
Run verification loop to validate implementation.
guard
Manually run the Hydra security and quality scan on specified files or directories.
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.
playwright-setup
Verify Playwright CLI installation and create a .playwright/cli.config.json configuration file. Use when setting up browser automation, configuring Playwright, or user mentions "setup playwright", "configure browser testing", "install playwright".
verify-upgrade
Verify Spring Boot project upgrade readiness with parallel multi-skill analysis.