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-dsgvo)<a href="https://agentmods.dev/commands/jonase47/ccpr/p6-audit-dsgvo"><img src="https://agentmods.dev/badge/commands/jonase47/ccpr/p6-audit-dsgvo.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.1 | $0.00000 | $0.00861 |
| Opus 5 | $0.00000 | $0.00430 |
| Sonnet 5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
p6-audit-dsgvo 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/p6-audit-dsgvo – DSGVO (GDPR) Compliance Check
Compares the implementation against the DSGVO initial assessment: data subject rights, data minimisation, deletion deadlines, data processing agreements.
Argument: $ARGUMENTS = [data category/area]
If provided: Focus on the specified area. If not provided: Check full DSGVO compliance.
Prerequisites
- DSGVO_INITIAL_ASSESSMENT.md present
- Implementation complete
Agent
- Type: security-master
- Model: sonnet
Context (Orchestrator prepares)
Orchestrator reads in advance and delivers inline:
- From DSGVO_INITIAL_ASSESSMENT.md: Data protection obligations, data categories
- From src/: Code that processes personal data (relevant sections only)
- From ARCHITECTURE.md: Data flow diagram (relevant section only)
Prompt Template
Goal: DSGVO compliance check against DSGVO_INITIAL_ASSESSMENT.md
DSGVO Requirements: [inline from DSGVO_INITIAL_ASSESSMENT.md]
Data-processing Code: [inline from src/]
Output Format: Checklist:
# DSGVO Requirement Implemented? Finding Overall assessment: COMPLIANT / FINDINGS / NON-COMPLIANT
Constraints:
- DSGVO check ONLY – no technical security
- For projects without personal data: brief confirmation is sufficient
- Focus on actual data processing, not theoretical
Orchestrator Checkpoint
- All points from DSGVO_INITIAL_ASSESSMENT.md checked?
- Findings correctly classified from a legal perspective?
Write Detail File
Write the result to docs/quality/audit_dsgvo.md (overwrite). Frontmatter:
---
phase: P6
subskill: audit-dsgvo
status: active
last_updated: <DD.MM.YYYY>
---
Body sections: ## Scope, ## Findings (DSGVO compliance checklist), ## 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_dsgvo.md](audit_dsgvo.md)with statuscomplete. - Lift any unmitigated Art. 6 / Art. 9 / Art. 13 finding into Open Risks.
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 Changed 9fa4618e137b
- 4d ago First seen · 91 lines · 0 tokens per session scan A ad6af54159d5
p6-audit-dsgvo is a command published in the GitHub repository jonase47/ccpr (1 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 861 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
compliance
Generate compliance-as-code policies with automated evidence. Usage - /mindforge:compliance [--framework soc2|hipaa|pci] [--engine opa|sentinel].
mindforge:fintech
Design fintech payment/ledger architecture. Usage: /mindforge:fintech [service] [--domain payments|ledger|kyc] [--compliance pci|sox].
mindforge:healthcare
Design HIPAA-compliant healthcare system architecture. Usage: /mindforge:healthcare [service] [--standard hipaa|hl7|fhir] [--scope full|audit].
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).