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 soar-patternsgit 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/soar-patterns)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/soar-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/soar-patterns/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/soar-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/soar-patterns.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.00049 | $0.02984 |
| Opus 5.5 | $0.00020 | $0.01194 |
| Sonnet 5.5 | $0.00010 | $0.00597 |
| Haiku 4.5 | $0.00005 | $0.00298 |
Grade A, and why
soar-patterns 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 — 332 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SOAR Patterns
Playbook design patterns, orchestration architecture, and integration strategies for security automation platforms.
Knowledge Base
SOAR Architecture Components
Orchestration: Coordinating actions across multiple security tools through a central platform. The SOAR platform acts as the conductor, calling APIs, passing data between tools, and managing the workflow state.
Automation: Executing predefined actions without human intervention. Ranges from simple (enrich an IP) to complex (isolate an endpoint, disable an account, block a domain, create a ticket, notify stakeholders).
Response: The actions taken to contain, remediate, and recover from a security incident. SOAR codifies response procedures as executable playbooks.
Playbook Categories
| Category | Trigger | Risk Level | Human Approval |
|---|---|---|---|
| Enrichment | Every alert | None (read-only) | Not required |
| Triage | Every alert | Low (classification) | Not required |
| Notification | Severity threshold | None (informational) | Not required |
| Investigation | Analyst-initiated | Low (queries only) | Optional |
| Containment | Confirmed threat | Medium-High (action) | Required initially |
| Remediation | Post-containment | High (changes systems) | Required |
| Recovery | Post-remediation | Medium (restores) | Required |
Platform Comparison
| Feature | Shuffle (OSS) | TheHive/Cortex (OSS) | Tines | Splunk SOAR | XSOAR |
|---|---|---|---|---|---|
| Cost | Free | Free | $$ | $$$ | $$$ |
| No-code builder | Yes | Partial | Yes | Yes | Yes |
| Custom code | Python, Go | Python (Cortex analyzers) | Ruby/JS | Python | Python/JS |
| Integrations | 100+ | 150+ (Cortex) | 200+ | 350+ | 700+ |
| Self-hosted | Yes | Yes | No | Yes | Yes |
| Case management | No (external) | Yes (built-in) | No (external) | No (external) | Yes |
| Community | Growing | Mature | Growing | Mature | Large |
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 · +49 tokens per session 8dc1e254583b
- 1mo ago First seen · 327 lines · 0 tokens per session scan A be85502e9bad
soar-patterns is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 2,984 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.