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 skills add HermeticOrmus/LibreSecOps-Claude-Code --skill security-policy-templatesgit 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/skills/hermeticormus/libresecops-claude-code/security-policy-templates)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/security-policy-templates"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/security-policy-templates/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/skills/hermeticormus/libresecops-claude-code/security-policy-templates"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/security-policy-templates.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.00058 | $0.01906 |
| Opus 5.5 | $0.00023 | $0.00762 |
| Sonnet 5.5 | $0.00012 | $0.00381 |
| Haiku 4.5 | $0.00006 | $0.00191 |
Grade A, and why
security-policy-templates 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 12d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Policy Templates
Reference templates and frameworks for common security policies with guidance on customization, enforcement, and regulatory alignment.
Knowledge Base
Policy Hierarchy
Security documentation follows a hierarchy from abstract to specific:
Policies (WHAT must be done - approved by leadership)
└─ Standards (HOW to comply - specific requirements)
└─ Procedures (STEP-BY-STEP - operational instructions)
└─ Guidelines (RECOMMENDATIONS - best practices, optional)
Policies are mandatory, approved by senior management, and change infrequently. They state requirements without prescribing specific technologies.
Standards define specific technical requirements that implement policies. They reference specific technologies, configurations, and metrics.
Procedures provide step-by-step operational instructions for carrying out standards. They are the most frequently updated documents.
Guidelines are recommendations and best practices. They are not mandatory but represent organizational wisdom.
Essential Policy Set
Every organization needs these core policies as a minimum:
| Policy | Purpose | Key Content |
|---|---|---|
| Acceptable Use | Defines acceptable use of organizational IT resources | Permitted/prohibited activities, personal use limits, monitoring notice |
| Information Classification | Defines data sensitivity levels and handling requirements | Classification levels, labeling, handling, sharing, disposal by level |
| Access Control | Governs who gets access to what and how | Least privilege, need-to-know, account lifecycle, privileged access |
| Incident Reporting | Defines how to report security events | What to report, how to report, when to report, who to contact |
| Password/Authentication | Defines credential requirements | Length, complexity, MFA requirements, storage, sharing prohibition |
| Data Retention & Disposal | Defines how long data is kept and how it is destroyed | Retention schedules by data type, secure disposal methods |
| Remote Work | Governs security for remote/hybrid workers | VPN, device security, physical workspace, network requirements |
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.
- 12d ago Changed · +5 lines · +58 tokens per session 64783d33dd29
- 1mo ago First seen · 147 lines · 0 tokens per session scan A 05cbf52e47a8
security-policy-templates is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 58 tokens to every session and 1,906 once invoked, about $0.0002 per session on Opus 5.5. 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 skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.