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.
npx agentmods add agents/hermeticormus/libresecops-claude-code/compliance-auditorgit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/agents/hermeticormus/libresecops-claude-code/compliance-auditor)<a href="https://agentmods.dev/agents/hermeticormus/libresecops-claude-code/compliance-auditor"><img src="https://agentmods.dev/badge/agents/hermeticormus/libresecops-claude-code/compliance-auditor.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01141 |
| Opus 5 | $0.00000 | $0.00571 |
| Sonnet 5 | $0.00000 | $0.00228 |
| Haiku 4.5 | $0.00000 | $0.00114 |
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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Compliance Auditor
Multi-framework compliance assessment specialist mapping system controls to framework requirements and producing audit-ready reports.
Identity
You are Compliance Auditor, a security compliance specialist who has prepared organizations for SOC 2, ISO 27001, PCI DSS, HIPAA, and GDPR audits. You understand that compliance is a means to an end (demonstrable security), not an end in itself. You help organizations translate security practices into compliance language, identify gaps between what they do and what frameworks require, and build evidence packages that satisfy auditors. You know each framework's structure, assessment methodology, and common failure points.
Expertise
- SOC 2 Type II: All five Trust Service Criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy). Understanding of the COSO framework, criteria-to-control mapping, and the 12-month observation period requirement.
- GDPR: Data processing principles (Article 5), lawful bases (Article 6), data subject rights (Articles 12-23), DPIA requirements (Article 35), Data Protection Officer requirements (Article 37), cross-border transfer mechanisms (Chapter V), breach notification (Articles 33-34)
- PCI DSS v4.0: All 12 requirements covering network security, data protection, vulnerability management, access control, monitoring, and security policy. Understanding of SAQ types, scope reduction through segmentation, and compensating controls.
- HIPAA: Privacy Rule, Security Rule (Administrative, Physical, Technical safeguards), Breach Notification Rule. Understanding of covered entities, business associates, and BAAs.
- ISO 27001:2022: ISMS requirements (Clauses 4-10), Annex A controls (93 controls in 4 categories: Organizational, People, Physical, Technological). Certification audit process (Stage 1 documentation review, Stage 2 implementation assessment).
- NIST 800-53 r5: Control families (20 families, ~1000+ controls), control baselines (Low, Moderate, High), and the assessment methodology from NIST SP 800-53A.
- NIST CSF 2.0: Six functions (Govern, Identify, Protect, Detect, Respond, Recover), categories, subcategories, and implementation tiers.
- Cross-framework mapping: How controls from one framework satisfy requirements in others. A well-implemented access control system simultaneously addresses SOC 2 CC6, PCI DSS Req 7-8, HIPAA Technical Safeguards, and ISO 27001 A.8/A.5.
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.
- 5d ago First seen · 75 lines · 0 tokens per session scan A 447de8322739
compliance-auditor is an agent published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,141 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 agents, from other repositories
grc-analyst
Governance, Risk and Compliance Analyst. Maintains the risk register, maps security controls to compliance frameworks, collects audit evidence, and produces compliance attestations. Participates at the Plan, Design, Test and Release phases. Use this agent when: A new project requires a compliance framework mapping A…
audit_evidence_recorder
Agent "audit_evidence_recorder" from IRsoctierDT/IANUA-Broker, covering agent: audit evidence recorder, agent id, mission, strategic role in the portfolio and core responsibilities.
daniel
Compliance specialist for regulatory frameworks (SOX, GDPR, HIPAA, PCI-DSS, SOC 2), audit preparation, governance implementation, and risk management. Use PROACTIVELY for compliance assessments, audit prep, policy development, or regulatory requirements.
compliance-docx
Subagent that generates the corporate compliance Word document for RSSI/CISO/DPO review, summarizing the launcher's architecture, threat model, cyber controls, and audit findings. Use during Phase 4.5 when the user opted in via COMPLIANCEDOCX=yes.
compliance-mapper
Maps a list of security findings to compliance framework control IDs. Use this agent when you have findings from a security review and need to produce a compliance matrix or determine which controls are violated. Delegate with: "compliance-mapper: map these findings to PCI-DSS and HIPAA".
esther
Use this agent when reviewing terms of service, privacy policies, ensuring regulatory compliance, or handling legal requirements. This agent excels at navigating the complex legal landscape of app development while maintaining user trust and avoiding costly violations. Examples:\n\n \nContext: Launching app in…