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-audit-config)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-audit-config"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-audit-config/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-audit-config"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-audit-config.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.00828 |
| Opus 5.5 | $0.00000 | $0.00331 |
| Sonnet 5.5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
p6-audit-config 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- p6-audit-deps — 86% identical, 55 lines differ
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-audit-config – Review Infrastructure & Configuration
Checks security headers, CORS, DB access, secrets management, and server configuration.
Argument: $ARGUMENTS = [configuration area]
If provided: Focus on the specified area. If not provided: Check the entire configuration.
Prerequisites
- Deployment configuration present
- SECURITY.md with infrastructure requirements
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- Configuration files: .env.example, Docker config, server config, etc.
- From src/: Security header configuration, CORS setup
- From SECURITY.md: Infrastructure requirements
Prompt Template
Goal: Check infrastructure and configuration security
Configuration: [inline from config files]
Output Format: Checklist:
# Check Point Status Finding 1 Security Headers (CSP, HSTS, X-Frame) OK/FINDING/N/A ... 2 CORS configuration OK/FINDING/N/A ... 3 DB access (least privilege) OK/FINDING/N/A ... 4 Secrets management OK/FINDING/N/A ... Constraints:
- Configuration check ONLY – no code review, no dependencies
- For static sites without a server: brief confirmation "N/A" is sufficient
- Focus on production configuration
Orchestrator Checkpoint
- All infrastructure points from SECURITY.md checked?
- Findings with concrete fix recommendation?
Write Detail File
Write the result to docs/quality/audit_config.md (overwrite). Frontmatter:
---
phase: P6
subskill: audit-config
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Findings, ## Severity Summary.
Update Sub-Index
Update docs/quality/AUDIT.md:
- Set
**Last Updated:** <DD.MM.YYYY>. - In its Detail Files table: ensure a row for
[audit_config.md](audit_config.md)with statuscomplete. - Lift any High/Critical config finding into Open Risks of the sub-index.
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 c5a7605c691f
- 1mo ago First seen · 90 lines · 0 tokens per session scan A e3ce1e02b6c9
p6-audit-config is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed 29d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 828 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
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
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.
create-pr
Context-aware GitHub Pull Request creation and update assistant.
forge-compact-task
Compact context with dotforge-standardized hint that preserves decisions, files modified, pending TODOs, behaviors disabled, and last commit. Use at 80% context window instead of waiting for auto-compact.
_conventions
Every slash command in this plugin follows a consistent structure so that the AI agent produces reliable, verifiable results. When authoring or updating a command file, include all of the sections below.