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-auditgit 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)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-audit"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-audit.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.00879 |
| Opus 5 | $0.00000 | $0.00439 |
| Sonnet 5 | $0.00000 | $0.00176 |
| Haiku 4.5 | $0.00000 | $0.00088 |
Grade A, and why
p6-audit 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-audit – Security Audit, Dependency Check & DSGVO (GDPR) Compliance
Conducts a defensive security audit. Each audit area is a separate sub-skill.
Argument: $ARGUMENTS = [focus/area]
If provided: Focus the audit on the specified area. If not provided: Run all audit areas.
Flow
0. Ensure Sub-Index Exists
Make sure docs/quality/AUDIT.md exists as a sub-index with the standard header (Status / Last Updated / Key Decisions / Open Risks / Detail Files / Gate Notes — see ~/.claude/docs/PROJECT_PHASES.md). If missing, create it with empty placeholders. The five p6-audit-* sub-skills below each refresh their own row in this sub-index's Detail Files table.
1. Static Code Analysis
/p6-audit-sast $ARGUMENTS – Checks code for injection, cryptography, secrets.
2. Auth Implementation
/p6-audit-auth $ARGUMENTS – Compares auth code against SECURITY.md.
3. Dependency Check
/p6-audit-deps $ARGUMENTS – Checks dependencies for CVEs.
4. Configuration
/p6-audit-config $ARGUMENTS – Checks security headers, CORS, secrets management.
5. DSGVO Compliance
/p6-audit-dsgvo $ARGUMENTS – Compares against DSGVO_INITIAL_ASSESSMENT.md.
6. Roll Up Sub-Index to Phase Index
After all p6-audit-* sub-skills have run, summarise the AUDIT sub-index into the phase index docs/quality/QA.md:
- Add an entry in the phase-index Detail Files table for
[AUDIT.md](AUDIT.md)(the sub-index itself), statuscompleteonce all five sub-skill rows arecomplete(orneeds-rework). - Lift any High/Critical audit finding into the phase-index Open Risks.
Notes
- Sub-skills 1–4 can run in parallel (no dependencies)
- DSGVO (5) can also run in parallel
- Detail files:
audit_sast.md,audit_auth.md,audit_deps.md,audit_config.md,audit_dsgvo.mdunder theAUDIT.mdsub-index - For minimal scope (no auth, no deps, no PII): abbreviate affected sub-skills with
status: activeand a body note stating "N/A — out of scope for "
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 · 63 lines · 0 tokens per session scan A 55ee087d73e2
p6-audit 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 879 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
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
wiki-tune
Tune wiki schema and conventions interactively.
listen
Show what a given agent should read before coding, plus briefs/approvals mentioning it.
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.
CLAUDE
Each subdirectory is one engine verb dispatched by ../cli/cli.ts: / .ts exports a pure handler that resolves the vault, does its work through ../core/ primitives, and returns its own typed report. Commands stay thin — they compose core checks and builders; they do not reimplement them. The canonical output schema is…