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 vulnerability-prioritizationgit 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/vulnerability-prioritization)<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/vulnerability-prioritization"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/vulnerability-prioritization/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/vulnerability-prioritization"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/vulnerability-prioritization.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.00057 | $0.01444 |
| Opus 5.5 | $0.00023 | $0.00578 |
| Sonnet 5 | $0.00011 | $0.00289 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
vulnerability-prioritization 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Prioritization
CVSS alone ranks too many things "critical". Prioritize by exploitation evidence, then likelihood, then impact in this environment. Aligns with NIST CSF 2.0 ID.RA, NIST SP 800-53r5 RA-5 / SI-2, CIS Controls v8.1 Control 7 (Continuous Vulnerability Management), and NIST SP 800-40r4 (enterprise patch management as preventive maintenance).
What Wazuh gives you
The vulnerability detector matches the syscollector package inventory against CVE feeds
and raises one alert per CVE and package, with fields under data.vulnerability.*:
cve, severity, cvss.cvss3.base_score (or score.base), package.name,
package.version, status (Active / Solved), published, reference.
| Rule | Level | Meaning |
|---|---|---|
| rule 23503 | 5 | Active, severity Low |
| rule 23504 | 7 | Active, severity Medium or Untriaged |
| rule 23505 | 10 | Active, severity High |
| rule 23506 | 13 | Active, severity Critical |
| rule 23502 | 3 | CVE no longer affects the package (solved, e.g. after an upgrade) |
| rule 23507 | 3 | vulnerabilities cleared for the agent |
So the alert level is just the vendor severity. It says nothing about exploitation or exposure, and that's what this skill adds. rules 23502 and 23507 are good remediation evidence: use them to confirm a fix instead of re-scanning. Detection lags the package scan interval, so note data freshness.
For configuration weaknesses on the same hosts (open services, weak SSH settings), load
wazuh-sca-hardening. SCA failures often turn a Track item into Attend.
Data gathering
get_wazuh_vulnerability_summary— counts by severity and top CVEs.get_wazuh_critical_vulnerabilities— the critical/high set with affected agents.get_wazuh_vulnerabilities(agent_id=...)— per-host detail when scoping.get_wazuh_vulnerabilities(agent_id=..., severity="critical")per host for scoping (vulnerability_assessmenton the MCP server is a prompt template, not a callable tool).get_agent_ports(agent_id)shows whether the vulnerable service is actually listening. That's your Exposure input.- For exploitation data use
search_external_contextwith the CVE id only: "CVE-XXXX-YYYY CISA KEV", "CVE-XXXX-YYYY EPSS". Never send hostnames.
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 · 106 lines · 57 tokens per session scan A 93016af6b9b5
vulnerability-prioritization is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (57 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 1,444 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.