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-gapgit 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-gap)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/compliance-gap"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/compliance-gap.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.01161 |
| Opus 5 | $0.00000 | $0.00580 |
| Sonnet 5 | $0.00000 | $0.00232 |
| Haiku 4.5 | $0.00000 | $0.00116 |
Grade A, and why
compliance-gap 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/compliance-gap
Identify specific compliance gaps between current state and framework requirements, with prioritized remediation roadmap.
Trigger
Use this command when:
- A compliance assessment has identified gaps that need remediation planning
- Preparing a remediation project plan before an upcoming audit
- Prioritizing security investments based on compliance requirements
- A customer or partner requires specific compliance certifications and you need to identify the work required
Input
Required:
- Framework: Target compliance framework
- Current state: Description of existing security controls, policies, and practices
Optional:
- Audit date: When the audit is scheduled (drives priority and timeline)
- Budget/resources: Available budget and team capacity (drives feasibility)
- Previous assessment: Results of prior compliance assessment for delta tracking
- Multi-framework: Additional frameworks to map gaps against (enables efficient multi-framework remediation)
Process
Step 1: Gap Identification
For each framework requirement, determine the gap type:
| Gap Type | Description | Example |
|---|---|---|
| Missing Control | No control exists to address the requirement | No vulnerability scanning program |
| Incomplete Control | Control exists but doesn't fully meet the requirement | Access reviews happen but not quarterly |
| Undocumented Control | Control exists and works but has no documentation | Backup process works but no policy exists |
| Missing Evidence | Control exists and is documented but evidence isn't collected | MFA is enforced but no enrollment reports are generated |
| Stale Evidence | Evidence exists but is outdated | Last penetration test was 18 months ago |
Step 2: Risk Assessment per Gap
For each gap, assess:
- Audit risk: Likelihood the auditor will test this control and the consequence of failure (exception, qualified opinion, material weakness)
- Security risk: Does this gap represent an actual security weakness or just a documentation gap?
- Business risk: Could this gap affect customer trust, contracts, or regulatory standing?
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.
- 4d ago First seen · 134 lines · 0 tokens per session scan A 942e1436cdc9
compliance-gap 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 1,161 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.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.