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/security-gategit clone --depth 1 https://github.com/HermeticOrmus/LibreSecOps-Claude-CodeWhat 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.00964 |
| Opus 5 | $0.00000 | $0.00482 |
| Sonnet 5 | $0.00000 | $0.00193 |
| Haiku 4.5 | $0.00000 | $0.00096 |
Grade A, and why
security-gate 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/security-gate
Define or modify quality gates that determine whether a build passes or fails based on security findings.
Trigger
Use when you need to:
- Define security gates for a new pipeline
- Adjust existing gate thresholds (too strict causing friction, or too loose letting vulns through)
- Add a gate for a specific scanner or finding type
- Implement differential gating (stricter for new code, lenient for existing)
Input
- Required: The CI/CD configuration file to modify or the pipeline platform being used
- Optional:
--scanner [sast|sca|dast|container|iac|secrets]-- configure gate for specific scanner - Optional:
--strategy [strict|balanced|permissive]-- preset threshold strategy - Optional:
--baseline-- establish a baseline of existing findings to suppress
Process
-
Current Gate Analysis: Review existing pipeline configuration for any quality gate definitions. Identify what thresholds are set, what scanners are gated, and what is warn-only.
-
Strategy Selection: Based on the requested strategy or interactive assessment:
Strict (new projects, security-critical applications):
- Block on any Critical or High finding
- Warn on Medium
- Log Low and Informational
- Zero tolerance for new secrets in code
Balanced (established projects, general applications):
- Block on Critical findings
- Block on High findings with EPSS > 10%
- Warn on other High and Medium
- Log Low
- Block on new secrets only (baseline suppression for existing)
Permissive (legacy codebases being onboarded, initial adoption):
- Block on Critical findings with known exploits (CISA KEV)
- Warn on Critical and High
- Log everything else
- Block on new secrets only
-
Differential Gating Configuration: Configure the pipeline to distinguish between:
- New findings (introduced in this PR/commit) -- stricter gates
- Existing findings (baseline) -- tracked but not blocking
- Suppressions (reviewed and accepted) -- excluded from gates
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.
- 2d ago First seen · 105 lines · 0 tokens per session scan A 9d0a64f42673
security-gate 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 964 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
redteam
Red Team Operations — 인프라 설정 보안 리뷰 + MITRE ATT&CK + Detection Engineering.
slsa
Check and improve SLSA compliance level.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
ci-report
Generate a CI failure report for PR $PRNUMORURL (or current branch if no argument given).
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.