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 automated-responsegit 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/automated-response)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/automated-response"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/automated-response/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/automated-response"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/automated-response.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.03128 |
| Opus 5 | $0.00000 | $0.01564 |
| Sonnet 5 | $0.00000 | $0.00626 |
| Haiku 4.5 | $0.00000 | $0.00313 |
Grade A, and why
automated-response 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 9d 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 — 344 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automated Response
Automated remediation patterns, containment actions, and the decision framework for when to automate versus when to require human approval.
Knowledge Base
The Automation Decision Framework
Not every action should be automated. The decision depends on three factors:
Reversibility: Can the action be undone easily? Blocking an IP is reversible (unblock it). Deleting data is not. Reversible actions are better candidates for automation.
Blast radius: What is the worst-case impact if the automation acts on a false positive? Isolating one endpoint is limited blast radius. Blocking a CDN IP range affects thousands of users.
Confidence: How certain is the detection that triggered the action? A verified IOC from multiple threat feeds warrants automated response. A single low-confidence alert does not.
Automation Decision Matrix:
High Confidence Low Confidence
┌─────────────────┬─────────────────┐
Reversible, │ AUTOMATE │ AUTOMATE with │
Low Blast Radius │ (no approval) │ approval gate │
├─────────────────┼─────────────────┤
Irreversible OR │ AUTOMATE with │ DO NOT │
High Blast Radius│ approval gate │ AUTOMATE │
└─────────────────┴─────────────────┘
Common Automated Response Actions
| Action | Tool | Reversibility | Blast Radius | Typical Approval |
|---|---|---|---|---|
| Block IP at firewall | Palo Alto, Fortinet API | Reversible | Low (single IP) | Auto for known-malicious |
| Isolate endpoint | CrowdStrike, SentinelOne API | Reversible | Medium (user impacted) | Approval required |
| Disable user account | Okta, Azure AD API | Reversible | Medium (user impacted) | Approval required |
| Quarantine email | M365, Proofpoint API | Reversible | Low (single email) | Auto for confirmed phishing |
| Block domain at DNS | DNS firewall API | Reversible | Low-Medium | Auto for known-malicious |
| Kill process | EDR API | Irreversible (process state lost) | Low | Auto for known malware |
| Delete file | EDR API, endpoint script | Irreversible | Low | Approval required |
| Reset password | IAM API | Partially reversible | Medium | Approval required |
| Revoke sessions | IAM API | Reversible (re-auth) | Medium | Auto for confirmed compromise |
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.
- 9d ago First seen · 344 lines · 0 tokens per session scan A 6eb1ad447319
automated-response is a skill 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 3,128 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 skills, from other repositories
building-devsecops-pipeline-with-gitlab-ci
Configure a GitLab CI/CD pipeline that embeds SAST (Semgrep, SpotBugs, Gosec, Bandit, NodeJsScan), DAST, container scanning, dependency scanning, and secret detection via GitLab's managed security templates. Use when building a shift-left DevSecOps pipeline in GitLab, adding automated vulnerability scanning stages to…
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…