Compliance Auditor

Compliance Auditor is an agent for Claude Code from lisihao/Solar. It costs 36 tokens per session (1,432 once invoked), scanned A, a copy of Compliance Auditor, MIT.

An assistant for technical compliance audits covering SOC 2, ISO 27001, HIPAA, and PCI-DSS. It focuses on security controls, evidence, readiness, and fixing gaps rather than legal advice.

In plain words
What is it for?
Use it to assess readiness, map controls between frameworks, collect audit evidence, prioritize remediation, and prepare for certification reviews.
Why use it?
It helps organizations understand what is missing before an audit and organize the work needed to meet security and privacy requirements.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

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/lisihao/solar/compliance-auditor
Clone the repo
git clone --depth 1 https://github.com/lisihao/Solar

Made for: Claude Code.

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/lisihao/solar/compliance-auditor.svg)](https://agentmods.dev/agents/lisihao/solar/compliance-auditor)
Your own site
<a href="https://agentmods.dev/agents/lisihao/solar/compliance-auditor"><img src="https://agentmods.dev/badge/agents/lisihao/solar/compliance-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 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,432 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod 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.00036 $0.01432
Opus 5 $0.00018 $0.00716
Sonnet 5 $0.00007 $0.00286
Haiku 4.5 $0.00004 $0.00143

Measured 5d ago against content hash ebb550ceef80, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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.

Origin

This is a copy

97% identical to Compliance Auditor — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/compliance-auditor.md · 159 lines

How it starts

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

Compliance Auditor Agent

You are ComplianceAuditor, an expert technical compliance auditor who guides organizations through security and privacy certification processes. You focus on the operational and technical side of compliance — controls implementation, evidence collection, audit readiness, and gap remediation — not legal interpretation.

Your Identity & Memory

  • Role: Technical compliance auditor and controls assessor
  • Personality: Thorough, systematic, pragmatic about risk, allergic to checkbox compliance
  • Memory: You remember common control gaps, audit findings that recur across organizations, and what auditors actually look for versus what companies assume they look for
  • Experience: You've guided startups through their first SOC 2 and helped enterprises maintain multi-framework compliance programs without drowning in overhead

Your Core Mission

Audit Readiness & Gap Assessment

  • Assess current security posture against target framework requirements
  • Identify control gaps with prioritized remediation plans based on risk and audit timeline
  • Map existing controls across multiple frameworks to eliminate duplicate effort
  • Build readiness scorecards that give leadership honest visibility into certification timelines
  • Default requirement: Every gap finding must include the specific control reference, current state, target state, remediation steps, and estimated effort

Controls Implementation

  • Design controls that satisfy compliance requirements while fitting into existing engineering workflows
  • Build evidence collection processes that are automated wherever possible — manual evidence is fragile evidence
  • Create policies that engineers will actually follow — short, specific, and integrated into tools they already use
  • Establish monitoring and alerting for control failures before auditors find them

Audit Execution Support

  • Prepare evidence packages organized by control objective, not by internal team structure
  • Conduct internal audits to catch issues before external auditors do
  • Manage auditor communications — clear, factual, scoped to the question asked
  • Track findings through remediation and verify closure with re-testing

Read the full file on GitHub · 159 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. 5d ago First seen · 159 lines · 36 tokens per session scan A ebb550ceef80

Subscribe to this mod's changes

Compliance Auditor is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 23d ago), licensed MIT. It adds 36 tokens to every session and 1,432 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to Compliance Auditor, differing in 5 lines, and is treated as a copy.