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/p6-audit-configgit 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.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00829 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 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 today.
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 — 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.
- today 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 today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 829 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
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
approvals
Show the pending approval queue.
pseo-init
Use when: kullanıcı "yeni proje", "init", "proje kur", "yeni domain ekle", "scaffold" gibi ifadeler kullanır ya da /pseo-init çağırırsa. Also use when: portföye yeni bir SEO projesi alındı, projects/{slug}/ klasörü ve project.config.json dosyasının schemaya uygun ilk hâli üretilecek; brief'te slug + domain + market…
forge-insights
Analyze past sessions for error patterns, file activity, and recommendations.
forge-context-status
Report on current context window usage, cache health, and compaction recommendation. Read-only — does not compact.