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-rules-and-decodersgit 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-rules-and-decoders)<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/wazuh-rules-and-decoders"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-rules-and-decoders/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-rules-and-decoders"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-rules-and-decoders.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.00062 | $0.01452 |
| Opus 5.5 | $0.00025 | $0.00581 |
| Sonnet 5 | $0.00012 | $0.00290 |
| Haiku 4.5 | $0.00006 | $0.00145 |
Grade A, and why
wazuh-rules-and-decoders 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Wazuh Rules and Decoders
A Wazuh alert is the output of a decoder (which parses a raw log into fields) and a rule (which matches those fields). Misreading the rule is the most common triage error. References below are from the stock Wazuh 4.14 ruleset.
Alert anatomy
| Field | Meaning |
|---|---|
rule.id, rule.level, rule.description |
Which rule fired and how severe Wazuh considers it |
rule.groups |
Categories (e.g. sshd, authentication_failed, syscheck) plus compliance tags |
rule.firedtimes |
How often this rule has fired for this agent since the manager started — high counts mean recurring noise or a sustained attack |
rule.mitre.id / tactic / technique |
ATT&CK mapping shipped with the rule (may be empty) |
rule.frequency |
Present on correlation rules: the threshold that triggered |
agent.id / name / ip |
The endpoint that produced the log (000 = the manager) |
manager.name |
Which manager/cluster node processed it |
decoder.name / decoder.parent |
Which decoder parsed the log (e.g. sshd, windows_eventchannel, json) |
data.* |
Decoded fields: data.srcip, data.srcuser, data.dstuser, data.win.*, data.aws.* … |
syscheck.* |
FIM fields (only on syscheck alerts) |
full_log |
The raw log line — attacker-controllable text |
location |
Source: file path, EventChannel, syscheck, rootcheck, integration name |
Level scale (0–15)
| Level | Wazuh meaning | Handling |
|---|---|---|
| 0 | Ignored / grouping rule, no alert | Never alerts; used as parents and for suppression |
| 2–4 | System notifications, low-relevance errors, successful events | Context only |
| 5–7 | User-generated errors, "bad word" matches, first-time or low-impact events | Watch for patterns |
| 8–10 | First-time-seen events, repeated errors, possible attacks | Triage |
| 11–12 | Integrity/important security events | Prioritize |
| 13–15 | High-importance events, attacks with high likelihood of success | Immediate |
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 · 96 lines · 62 tokens per session scan A 5032e9a59c1b
wazuh-rules-and-decoders is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (57 stars, last pushed 2d ago), licensed MIT. It adds 62 tokens to every session and 1,452 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-performance-optimizer
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer.
agent-refinement
Agent skill for refinement - invoke with $agent-refinement.
diag-harness
Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.
building-detection-rule-with-splunk-spl
Build effective detection rules using Splunk Search Processing Language (SPL) correlation searches to identify security threats in SOC environments.
nio-scan
Nio code/skill execution-risk scanner. Use when the user wants to scan a file, repo, directory, or skill for execution risks — e.g. "scan this code for risks", "is this file/plugin dangerous", "check this repo for malicious code", "run nio scan on ". Focused single-purpose skill; for other Nio operations use /nio.
nio-doctor
Nio config validator + connectivity check. Use when the user wants to validate their Nio setup — e.g. "run nio doctor", "is my nio config valid / working", "test my OAuth / external endpoint / LLM connectivity", "why isn't my scorer firing". Focused single-purpose skill; for other Nio operations use /nio.