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.
git 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/security-policy)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/security-policy"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/security-policy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/security-policy"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/security-policy.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01061 |
| Opus 5 | $0.00000 | $0.00531 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
security-policy 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 6d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/security-policy
Generate a security policy document tailored to organizational context, regulatory requirements, and workforce profile.
Trigger
Use when creating new security policies or updating existing ones. Appropriate for:
- Establishing a security policy framework for a new organization
- Updating policies for regulatory compliance (GDPR, HIPAA, SOC 2, PCI-DSS)
- Creating role-specific policies (developer security, remote work, BYOD)
- Standardizing informal security practices into formal documentation
- Preparing for security audits or certifications
Input
- Policy type: Which policy to create. Options include:
- Acceptable Use Policy
- Information Classification and Handling
- Incident Reporting and Response
- Access Control and Authentication
- Password and Credential Management
- Remote Work and BYOD
- Data Retention and Disposal
- Vendor and Third-Party Risk
- Change Management
- Physical Security
- Social Media and Public Communication
- Encryption and Key Management
- Network Security
- Mobile Device Management
- Organization context: Industry, size, risk profile, existing policies
- Regulatory requirements: Applicable regulations and standards
- Audience: Who the policy applies to (all employees, IT staff, contractors, etc.)
- Enforcement model: How violations are handled in the organization
- Existing policies (optional): Related policies already in place for cross-referencing
Process
-
Requirements gathering -- Identify the regulatory, business, and risk requirements the policy must address
-
Scope definition -- Determine who the policy applies to, what systems/data/activities it covers, and any explicit exclusions
-
Policy drafting -- Write the policy in clear, direct language:
- Use active voice ("You must..." not "It is required that...")
- Provide concrete examples for abstract requirements
- Include the rationale for each requirement
- Avoid unnecessary jargon (or define it in a glossary)
- Keep sentences short and paragraphs focused on one topic
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.
- 6d ago First seen · 147 lines · 0 tokens per session scan A 489dd26cc4ec
security-policy 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,061 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-09-03.
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.