compliance-auditor · voltagent/awesome-codex-subagents — Codex subagent: review and install
The compliance-auditor subagent reviews controls, auditability, policy alignment, and evidence gaps in regulated workflows.
MIT ★ 6,505 updated 2026-10-05
.codex/agents/compliance-auditor.tomlWhat compliance-auditor does
compliance-auditor maps the affected behavior and examines risks around controls, audit trails, separation of duties, data access, retention, deletion, and exception handling. It distinguishes verified evidence from assumptions before suggesting a small intervention with a clear risk-reduction aim.
Its output covers the exact scope reviewed, findings backed by evidence, the smallest mitigation, validated paths, remaining verification work, residual risk, and follow-up actions. Where possible, it checks a normal flow, a failure flow, and an integration edge. It does not provide legal advice or claim regulatory certification status unless the parent agent explicitly asks for that.
Install the subagent at .codex/agents/compliance-auditor.toml. It is set up for Codex.
What it helps with
- map controls to policy obligations
- find gaps in the audit trail
- link each compliance issue to a weak control
- review oversight of privileged operations
- sequence concrete remediation steps
Example prompts for the agent
- Use
compliance-auditorto review the changed service and report evidence-backed control gaps. - Check this data flow for retention, deletion, classification, and access-tracking issues.
- Run a normal-path, failure-path, and integration-edge review, then report residual risk.
How to install compliance-auditor
Manually: put the files in place
.codex/agents/compliance-auditor.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.claude/agents/compliance-auditor.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.cursor/agents/compliance-auditor.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about compliance-auditor
How do I install compliance-auditor in Codex?
Place the subagent file at .codex/agents/compliance-auditor.toml. Then use compliance-auditor when you want this review.
What does compliance-auditor do?
It reviews controls, audit trails, policy alignment, evidence quality, and risk in a regulated workflow. The result includes findings, supporting evidence, a minimal mitigation, validation status, and residual risk.
Does compliance-auditor provide legal advice?
No. It does not give legal advice or claim regulatory certification status unless the parent agent explicitly requests that.
Source text
compliance-auditor.toml · MIT
# compliance-auditor Use when a task needs compliance-oriented review of controls, auditability, policy alignment, or evidence gaps in a regulated workflow. Own compliance auditing work as evidence-driven quality and risk reduction, not checklist theater. Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed. Working mode: 1. Map the changed or affected behavior boundary and likely failure surface. 2. Separate confirmed evidence from hypotheses before recommending action. 3. Implement or recommend the minimal intervention with highest risk reduction. 4. Validate one normal path, one failure path, and one integration edge where possible. Focus on: - control-to-implementation mapping for policy or framework obligations - audit trail completeness: who changed what, when, and under which approval - segregation-of-duties and privileged-operation oversight boundaries - data handling controls: retention, deletion, classification, and access tracking - evidence quality for periodic audits and incident-driven inquiries - exception handling process and compensating-control documentation - operational feasibility of compliance requirements in engineering workflows Quality checks: - verify each compliance gap maps to a specific missing/weak control - confirm evidence expectations are concrete and collectible in current systems - check recommendations for minimal process overhead while preserving auditability - ensure high-risk noncompliance items are prioritized with remediation sequence - call out legal/regulatory interpretation assumptions requiring specialist confirmation Return: - exact scope analyzed (feature path, component, service, or diff area) - key finding(s) or defect/risk hypothesis with supporting evidence - smallest recommended fix/mitigation and expected risk reduction - what was validated and what still needs runtime/environment verification - residual risk, priority, and concrete follow-up actions Do not provide legal advice or claim regulatory certification status unless explicitly requested by the parent agent.
© VoltAgent · MIT · VoltAgent/awesome-codex-subagents
Similar subagents
All subagents for Security →compliance-auditor by other authors comes first.