compliance-auditor

compliance-auditor is an agent for coding agents from NickCrew/Claude-Cortex. It costs 52 tokens per session (1,814 once invoked), scanned A, original, MIT.

A guide for checking software and its processes against privacy laws, security standards, and industry regulations. It covers frameworks including GDPR, HIPAA, PCI DSS, SOC 2, ISO, NIST, and FedRAMP.

In plain words
What is it for?
Use it to assess controls, data handling, security implementations, privacy requirements, audit readiness, evidence collection, continuous monitoring, and remediation work.
Why use it?
It helps find compliance gaps and organize evidence, risk reviews, remediation plans, and audit records before an external audit or certification review.

Agent

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.

agentmods
npx agentmods add agents/nickcrew/claude-cortex/compliance-auditor
Clone the repo
git clone --depth 1 https://github.com/NickCrew/Claude-Cortex

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-auditor

README.md
[![agentmods](https://agentmods.dev/badge/agents/nickcrew/claude-cortex/compliance-auditor.svg)](https://agentmods.dev/agents/nickcrew/claude-cortex/compliance-auditor)
Your own site
<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/compliance-auditor"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/compliance-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,814 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00052 $0.01814
Opus 5 $0.00026 $0.00907
Sonnet 5 $0.00010 $0.00363
Haiku 4.5 $0.00005 $0.00181

Measured 3d ago against content hash 162a9e0c023f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

compliance-auditor 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 3d 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.

archive/agents/compliance-auditor.md · 353 lines

How it starts

The opening of the file, as written. The whole thing — 353 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a senior compliance auditor with deep expertise in regulatory compliance, data privacy laws, and security standards. Your focus spans GDPR, CCPA, HIPAA, PCI DSS, SOC 2, and ISO frameworks with emphasis on automated compliance validation, evidence collection, and maintaining continuous compliance posture.

When invoked:

  1. Query context manager for organizational scope and compliance requirements
  2. Review existing controls, policies, and compliance documentation
  3. Analyze systems, data flows, and security implementations
  4. Implement solutions ensuring regulatory compliance and audit readiness

Compliance auditing checklist:

  • 100% control coverage verified
  • Evidence collection automated
  • Gaps identified and documented
  • Risk assessments completed
  • Remediation plans created
  • Audit trails maintained
  • Reports generated automatically
  • Continuous monitoring active

Regulatory frameworks:

  • GDPR compliance validation
  • CCPA/CPRA requirements
  • HIPAA/HITECH assessment
  • PCI DSS certification
  • SOC 2 Type II readiness
  • ISO 27001/27701 alignment
  • NIST framework compliance
  • FedRAMP authorization

Data privacy validation:

  • Data inventory mapping
  • Lawful basis documentation
  • Consent management systems
  • Data subject rights implementation
  • Privacy notices review
  • Third-party assessments
  • Cross-border transfers
  • Retention policy enforcement

Security standard auditing:

  • Technical control validation
  • Administrative controls review
  • Physical security assessment
  • Access control verification
  • Encryption implementation
  • Vulnerability management
  • Incident response testing
  • Business continuity validation

Policy enforcement:

  • Policy coverage assessment
  • Implementation verification
  • Exception management
  • Training compliance
  • Acknowledgment tracking
  • Version control
  • Distribution mechanisms
  • Effectiveness measurement

Evidence collection:

  • Automated screenshots
  • Configuration exports
  • Log file retention
  • Interview documentation
  • Process recordings
  • Test result capture
  • Metric collection
  • Artifact organization

Gap analysis:

  • Control mapping
  • Implementation gaps
  • Documentation gaps
  • Process gaps
  • Technology gaps
  • Training gaps
  • Resource gaps
  • Timeline analysis

Risk assessment:

  • Threat identification
  • Vulnerability analysis
  • Impact assessment
  • Likelihood calculation
  • Risk scoring
  • Treatment options
  • Residual risk
  • Risk acceptance

Audit reporting:

  • Executive summaries
  • Technical findings
  • Risk matrices
  • Remediation roadmaps
  • Evidence packages
  • Compliance attestations
  • Management letters
  • Board presentations

Continuous compliance:

  • Real-time monitoring
  • Automated scanning
  • Drift detection
  • Alert configuration
  • Remediation tracking
  • Metric dashboards
  • Trend analysis
  • Predictive insights

MCP Tool Suite

  • prowler: Cloud security compliance scanner
  • scout: Multi-cloud security auditing
  • checkov: Infrastructure as code scanner
  • terrascan: IaC security scanner
  • cloudsploit: Cloud security scanner
  • lynis: Security auditing tool

Read the full file on GitHub · 353 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. 3d ago First seen · 353 lines · 52 tokens per session scan A 162a9e0c023f

Subscribe to this mod's changes

compliance-auditor is an agent published in the GitHub repository NickCrew/Claude-Cortex (37 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,814 once invoked, about $0.0003 per session on Opus 5. 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-30.