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 gensecaihq/Wazuh-Autopilot --skill wazuh-active-responsegit clone --depth 1 https://github.com/gensecaihq/Wazuh-AutopilotWrote 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/gensecaihq/wazuh-autopilot/wazuh-active-response)<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/wazuh-active-response"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-active-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/gensecaihq/wazuh-autopilot/wazuh-active-response"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-active-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.00053 | $0.01503 |
| Opus 5.5 | $0.00021 | $0.00601 |
| Sonnet 5 | $0.00011 | $0.00301 |
| Haiku 4.5 | $0.00005 | $0.00150 |
Grade A, and why
wazuh-active-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 yesterday.
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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wazuh Active Response
Agents never execute actions. The response-planner proposes (propose_action); the autonomy policy and
human approvers decide; the platform executor calls the Wazuh MCP action tool; the responder verifies.
This skill explains what happens underneath so plans are realistic and verification is honest.
How Wazuh AR works
- The Wazuh API (via the MCP server) sends an active-response command to one or more agents.
- The agent runs a script of that name from its active-response bin directory. If the script isn't deployed on that agent, nothing happens on the host.
- The API returns as soon as the manager accepts and dispatches the command ("AR command was sent to the agent") — this is not proof of execution.
- The script logs its outcome; Wazuh turns that log into an alert in the
active_responsegroup. - API-triggered AR is permanent: Wazuh ignores the timeout for API-triggered commands, so a block stays until explicitly removed (rollback), unlike rule-triggered AR with a timeout.
What each platform action sends
| Platform action | MCP tool | AR command | Stock script? | Rollback |
|---|---|---|---|---|
| block_ip | wazuh_block_ip | !firewall-drop (-srcip) on one agent or all_agents |
Yes | wazuh_firewall_allow — per agent; needs an undo script configured on the MCP server |
| firewall_drop | wazuh_firewall_drop | !firewall-drop |
Yes | wazuh_firewall_allow |
| host_deny | wazuh_host_deny | !host-deny (adds to /etc/hosts.deny, Linux) |
Yes | wazuh_host_allow |
| disable_user | wazuh_disable_user | !disable-account |
Yes (Linux) | wazuh_enable_user |
| isolate_host | wazuh_isolate_host | !host-isolation |
No — custom script required | wazuh_unisolate_host |
| kill_process | wazuh_kill_process | !kill-process (PID) |
No — custom script required | None |
| quarantine_file | wazuh_quarantine_file | !quarantine (path) |
No — custom script required | wazuh_restore_file |
| restart_wazuh | wazuh_restart | Wazuh API restart of agent or manager | n/a | n/a |
| active_response | wazuh_active_response | Allowlisted command names only | Depends | Depends |
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.
- yesterday First seen · 95 lines · 53 tokens per session scan A fdd165178c43
wazuh-active-response is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (57 stars, last pushed 2d ago), licensed MIT. It adds 53 tokens to every session and 1,503 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-25.
Other skills, from other repositories
agent-crdt-synchronizer
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer.
agent-topology-optimizer
Agent skill for topology-optimizer - invoke with $agent-topology-optimizer.
agent-benchmark-suite
Agent skill for benchmark-suite - invoke with $agent-benchmark-suite.
agent-performance-monitor
Agent skill for performance-monitor - invoke with $agent-performance-monitor.
agent-resource-allocator
Agent skill for resource-allocator - invoke with $agent-resource-allocator.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.