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/plugins/hermeticormus/libresecops-claude-code/incident-response)<a href="https://agentmods.dev/plugins/hermeticormus/libresecops-claude-code/incident-response"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libresecops-claude-code/incident-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/plugins/hermeticormus/libresecops-claude-code/incident-response"><img src="https://agentmods.dev/badge/plugins/hermeticormus/libresecops-claude-code/incident-response.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
incident-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 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.
What it actually says
{
"name": "incident-response",
"version": "1.0.0",
"description": "Security incident response: incident command and coordination, forensic evidence handling, playbooks for common incident types, and blameless postmortems.",
"author": {
"name": "Diego Bodart",
"url": "https://github.com/HermeticOrmus"
},
"homepage": "https://github.com/HermeticOrmus/LibreSecOps-Claude-Code",
"repository": "https://github.com/HermeticOrmus/LibreSecOps-Claude-Code",
"license": "MIT",
"keywords": [
"incident-response",
"dfir",
"forensics",
"playbooks",
"postmortem",
"nist-800-61"
]
}
What it installs
The manifest is a name and a version. 1 skill, 2 commands, 2 agents travel with it, and installing the plugin installs all of them — 267 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 First seen · 21 lines scan A 2a968fe0d8da
incident-response is a plugin published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-01.
Other plugins, from other repositories
shipproof
Evidence-first engineering and production audits for secure, efficient, scalable systems.
draugr
Security scanning for AI agents: SAST, SCA, secrets, IaC, DAST, ranked by real risk.
shor
Shor — autonomous AI web pentester. Provides the /shor-setup slash-command: an interactive wizard that guides you from zero to a running scan (black-box or white-box, GCP deployment included).
osv-advisory-mcp-server
Query OSV.dev for package vulnerabilities, batch-audit dependency lists, and fetch full advisory records via MCP. STDIO or Streamable HTTP.
humanizer
Rewrite AI-sounding text so it reads like the writer without changing what it says.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.