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 commands/hermeticormus/libresecops-claude-code/compliance-checkgit 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/commands/hermeticormus/libresecops-claude-code/compliance-check)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/compliance-check"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/compliance-check.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.00989 |
| Opus 5 | $0.00000 | $0.00495 |
| Sonnet 5 | $0.00000 | $0.00198 |
| Haiku 4.5 | $0.00000 | $0.00099 |
Grade A, and why
compliance-check 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/compliance-check
Assess a system against a specified compliance framework and produce a gap analysis report.
Trigger
Use this command when:
- Preparing for a compliance audit (SOC 2, ISO 27001, PCI DSS, etc.)
- Evaluating compliance posture of a new or existing system
- Determining which controls need to be implemented for a specific framework
- Mapping existing security controls to framework requirements
- Assessing readiness for a customer security questionnaire
Input
Required:
- Framework:
soc2,gdpr,pci-dss,hipaa,iso27001,nist-800-53,nist-csf
Optional:
- Scope: Description of in-scope systems, data types, and processes
- Profile/Level: For frameworks with tiers (NIST 800-53: Low/Moderate/High, ISO 27001: specific Annex A controls)
- Existing controls: Description of security measures already in place
- Exclusions: Controls known to be not applicable with justification
Process
Step 1: Scope Definition
- Identify the systems, data, and processes in scope for the framework
- Determine the applicable profile or tier level
- For PCI DSS: determine the cardholder data environment (CDE) boundaries
- For GDPR: identify personal data processing activities and legal bases
- For HIPAA: identify covered entities, business associates, and ePHI flows
- Document scope boundaries and exclusions with justifications
Step 2: Control Inventory
Based on the framework, enumerate all applicable controls:
SOC 2 (Trust Service Criteria):
- CC1: Control Environment (7 criteria)
- CC2: Communication and Information (3 criteria)
- CC3: Risk Assessment (4 criteria)
- CC4: Monitoring Activities (2 criteria)
- CC5: Control Activities (3 criteria)
- CC6: Logical and Physical Access Controls (8 criteria)
- CC7: System Operations (5 criteria)
- CC8: Change Management (1 criterion)
- CC9: Risk Mitigation (2 criteria)
- Plus criteria for selected additional categories (Availability, Processing Integrity, Confidentiality, Privacy)
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 · 127 lines · 0 tokens per session scan A 642603b09a72
compliance-check is a command 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 989 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 commands, from other repositories
scope
Mandatory pre-flight scope check — verify an asset is in scope BEFORE any HTTP touch. Deterministic (deny-wins, default-deny) via engine/scope.py against the engagement's scope.md. Blocks out-of-scope testing. Usage: /scope [ ...].
sicario.controls
Generate or update docs/compliance/control-applicability.md.
sicario.evidence
Generate evidence artifacts.
compliance-check
Check IaC files against a specific compliance framework.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.