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/TheLobbi/claudeWrote 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/thelobbi/claude/compliance-audit)<a href="https://agentmods.dev/commands/thelobbi/claude/compliance-audit"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/compliance-audit/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/thelobbi/claude/compliance-audit"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/compliance-audit.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.03197 |
| Opus 5.5 | $0.00000 | $0.01279 |
| Sonnet 5.5 | $0.00000 | $0.00639 |
| Haiku 4.5 | $0.00000 | $0.00320 |
Grade A, and why
compliance-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 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Audit
Full regulatory compliance audit for GDPR, HIPAA, SOC2, PCI-DSS, ISO 27001, and other frameworks with gap analysis, remediation planning, and evidence collection.
Purpose
Conduct comprehensive compliance audit against multiple regulatory frameworks to ensure legal and regulatory adherence, identify compliance gaps, create remediation plans, and prepare for external audits and certifications.
Multi-Agent Coordination Strategy
Uses parallel compliance assessment pattern where framework-specific agents audit in parallel, then synthesize findings for cross-framework compliance optimization.
Compliance Audit Architecture
``` ┌──────────────────────────────────────────────────┐ │ Compliance Command Center │ │ (compliance-orchestrator) │ └────────────┬─────────────────────────────────────┘ │ ┌────────┼────────┬────────┬────────┬─────────┐ ▼ ▼ ▼ ▼ ▼ ▼ GDPR HIPAA SOC2 PCI-DSS ISO27001 Custom ```
Execution Flow
Phase 1: Compliance Scoping (0-20 mins)
- compliance-orchestrator - Determine applicable frameworks
- scope-analyzer - Identify in-scope systems and data
- data-classifier - Classify data types (PII, PHI, PCI, etc.)
- stakeholder-mapper - Identify compliance stakeholders
Phase 2: GDPR Compliance Audit (20-50 mins)
- gdpr-auditor - GDPR Article compliance check
- data-subject-rights-validator - Right to access, erasure, portability
- consent-manager-auditor - Consent collection and management
- data-protection-impact-assessor - DPIA requirements
- international-transfer-validator - Cross-border data transfer compliance
- privacy-policy-reviewer - Privacy policy completeness
Phase 3: HIPAA Compliance Audit (50-80 mins)
- hipaa-auditor - HIPAA Security and Privacy Rule compliance
- phi-identifier - Protected Health Information identification
- access-control-validator - Minimum necessary and role-based access
- audit-log-validator - Audit logging requirements
- encryption-validator - PHI encryption at rest and in transit
- breach-notification-assessor - Breach notification procedures
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 First seen · 382 lines · 0 tokens per session scan A 91b4d5a9c4a6
compliance-audit is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,197 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-08-31.
Other commands, from other repositories
deps-audit
Audit project dependencies for vulnerabilities, outdated packages, license conflicts, and supply chain risks — then provide actionable remediation strategies.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.
app-store-audit
Run an enterprise pre submission compliance audit on an iOS or Android app against Apple App Store and Google Play rejection rules. Pass a project path or run from the project root.
auditoria-legal
Grupo: Trabajo con el framework En una frase: Auditoría de cumplimiento legal del producto — territorio, evidencia y lo que el código no cubre. Cuándo: Antes de publicar una app o web: registro, cookies, analítica, emails, suscripciones, contenido de usuarios. Quién: Cualquier operador del repo.