compliance-audit

compliance-audit is a command for Claude Code from TheLobbi/claude. It costs 0 tokens per session (3,197 once invoked), scanned A, original, MIT.

A command for checking systems and processes against regulations such as GDPR, the European Union privacy law, HIPAA, the US health-data law, and SOC 2, a security-controls standard. It identifies missing requirements, suggests fixes, and gathers audit evidence.

In plain words
What is it for?
Use it to scope an audit, assess systems against selected frameworks, plan remediation work, collect evidence, and prepare for external audits or certifications.
Why use it?
It helps teams find compliance gaps before a regulator, customer, or certification auditor does. It also brings findings from several frameworks into one review.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the claude-orchestration plugin — 6 skills, 133 commands, 9 agents, 8 hooks, 6 plugins shipped together

Good fit Use it to scope an audit, assess systems against selected frameworks, plan remediation work, collect evidence, and prepare for external audits or certifications.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thelobbi/claude/compliance-audit
Install

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.

Clone the repo
git clone --depth 1 https://github.com/TheLobbi/claude

Made for: Claude Code.

Or install claude-orchestration, the plugin that ships this one along with the rest of its 6 skills, 133 commands, 9 agents, 8 hooks, 6 plugins.

Wrote 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.

agentmods badge for compliance-audit

README.md
[![agentmods](https://agentmods.dev/badge/commands/thelobbi/claude/compliance-audit/github.svg)](https://agentmods.dev/commands/thelobbi/claude/compliance-audit)
Your own site
<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.

agentmods 80×15 button for compliance-audit

Your own site · 80×15
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,197 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.03197
Opus 5 $0.00000 $0.01598
Sonnet 5 $0.00000 $0.00639
Haiku 4.5 $0.00000 $0.00320

Measured 8d ago against content hash 91b4d5a9c4a6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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.

.claude/commands/compliance-audit.md · 382 lines

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)

  1. compliance-orchestrator - Determine applicable frameworks
  2. scope-analyzer - Identify in-scope systems and data
  3. data-classifier - Classify data types (PII, PHI, PCI, etc.)
  4. stakeholder-mapper - Identify compliance stakeholders

Phase 2: GDPR Compliance Audit (20-50 mins)

  1. gdpr-auditor - GDPR Article compliance check
  2. data-subject-rights-validator - Right to access, erasure, portability
  3. consent-manager-auditor - Consent collection and management
  4. data-protection-impact-assessor - DPIA requirements
  5. international-transfer-validator - Cross-border data transfer compliance
  6. privacy-policy-reviewer - Privacy policy completeness

Phase 3: HIPAA Compliance Audit (50-80 mins)

  1. hipaa-auditor - HIPAA Security and Privacy Rule compliance
  2. phi-identifier - Protected Health Information identification
  3. access-control-validator - Minimum necessary and role-based access
  4. audit-log-validator - Audit logging requirements
  5. encryption-validator - PHI encryption at rest and in transit
  6. breach-notification-assessor - Breach notification procedures

Read the full file on GitHub · 382 lines

Changes

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.

  1. 8d ago First seen · 382 lines · 0 tokens per session scan A 91b4d5a9c4a6

Subscribe to this mod's changes

compliance-audit is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 2d ago), 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.