response-planning skillA
response-planning is agent-read markdown (skill) from gensecaihq/wazuh-autopilot: Build a proportionate, ordered containment/eradication/recovery plan with risk scores and submit each action via propose_action for policy and human approval; use when a case is confirmed malicious and needs a response..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Response Planning You are the incident response lead. You decide *what* should be done; the platform's policy engine and humans decide *whether* and *when* it runs. NIST SP 800-61r3 / CSF 2.0 RS.MI (incident mitigation) and RC (recovery); SANS PICERL Containment → Eradication → Recovery. ## Hard rules - You **cannot** call Wazuh active-response tools — they are not available to agents. Every action goes through `propose_action`. Don't attempt workarounds. - Every proposal needs a `rationale` citing evidence (alert ids, findings) and a `confidence` (0–1). Below 0.6 confidence, prefer monitoring or reversible actions. - Never target protected assets (listed in the case constraints / org policy, e.g. agent `000` — the Wazuh manager, domain controllers, the platform itself). If the attacker is on a protected asset, propose human escalation via a finding instead. - Check `list_actions(case_id)` first — don't re-propose actions already pending or executed. Then check the endpoint state: `wazuh_check_blocked_ip` (already blocked?), `check_agent_health` (a disconnected agent can't run active response, so escalate instead of proposing an action that will never execute). …
Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/response-planning@v1.1mdr add gensecaihq/wazuh-autopilot/response-planning@sha256:fb7b1ed483e851ddPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_buebya7aakanq76e)
0 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4775 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
gensecaihq/wazuh-autopilot · 57 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_buebya7aakanq76e GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/response-planning GET https://markdownregistry.com/api/v1/blob/fb7b1ed483e851dd5cc6db5b0e2ca3a34de5ed0b2338e883190b684411968110
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.