threat-hunting

threat-hunting is a skill for Claude Code from gensecaihq/Wazuh-Autopilot. It costs 54 tokens per session (1,164 once invoked), scanned A, original, MIT.

A structured way to search security data for signs of attacks that existing alerts missed. It tests a specific idea, learns what normal activity looks like, or uses grouped data to find unusual behaviour.

In plain words
What is it for?
Use it for scheduled threat hunts, checking attacker behaviour in Wazuh data, and passing useful findings to the team that creates detections.
Why use it?
It looks beyond incoming alerts, helping find hidden or emerging attacks and turn confirmed patterns into better detections.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it for scheduled threat hunts, checking attacker behaviour in Wazuh data, and passing useful findings to the team that creates detections.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gensecaihq/wazuh-autopilot/threat-hunting
Install

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.

Any agent
npx skills add gensecaihq/Wazuh-Autopilot --skill threat-hunting
Clone the repo
git clone --depth 1 https://github.com/gensecaihq/Wazuh-Autopilot

Made for: Claude Code.

Wrote 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.

agentmods badge for threat-hunting

README.md
[![agentmods](https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/threat-hunting/github.svg)](https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/threat-hunting)
Your own site
<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/threat-hunting"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/threat-hunting/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.

agentmods 80×15 button for threat-hunting

Your own site · 80×15
<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/threat-hunting"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/threat-hunting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,164 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00054 $0.01164
Opus 5.5 $0.00022 $0.00466
Sonnet 5 $0.00011 $0.00233
Haiku 4.5 $0.00005 $0.00116

Measured yesterday against content hash 84fe81135d1c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-26, from the pricing page.

Security

Grade A, and why

threat-hunting 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.

backend/app/skills/threat-hunting/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Threat Hunting

Hunting assumes the attacker got past existing detections. NIST CSF 2.0 DE.CM / DE.AE — continuous monitoring and analysis beyond alert-driven work.

PEAK framework (Prepare → Execute → Act with Knowledge)

Three hunt types:

  1. Hypothesis-driven — test a specific idea about attacker behaviour.
  2. Baseline — characterize normal, then examine outliers (e.g. rare processes, rare parent-child pairs, rare outbound destinations).
  3. Model-assisted — use analytics/aggregation (analyze_alert_patterns, get_alerts_aggregated) to surface anomalies for human-style review.

TaHiTI (Targeted Hunting integrating Threat Intelligence) adds: start hunts from current threat intel, and feed results back into intel and detection.

Hypothesis template

Hypothesis: <actor behaviour> is occurring on <scope> and would appear as <observable> in <data source>.
ATT&CK: <technique id>
Data: <Wazuh rule groups / fields>
Time range: <e.g. 14d>
Success criteria: <what confirms / refutes>

Example: "An attacker has established persistence via cron on Linux servers; this would appear as FIM or audit events on /etc/cron* or /var/spool/cron outside change windows (T1053.003), last 14 days."

Hunt catalog (starting points)

Hunt Technique Query idea
Cron/systemd persistence T1053.003, T1543.002 FIM events (rule_groups=["syscheck"], rules 550, 554) on cron/systemd paths, aggregated by host
New local accounts T1136.001 rule 5902 (useradd) and rule 60109 (Event ID 4720) outside provisioning systems
Log clearing T1070.001/.002 Event ID 1102 / Event ID 104; FIM rule 553 or size drops on /var/log files
Encoded PowerShell T1059.001, T1027 Sysmon Event ID 1 / Event ID 4688 command lines containing -enc (rule_groups=["sysmon_eid1_detections"]); load wazuh-windows-sysmon
Rare outbound destinations T1071 aggregate firewall/proxy destinations, look at count = 1–2
SSH key additions T1098.004 FIM (rules 550, 554) on authorized_keys, only if monitored; see wazuh-fim-investigation
Web shells T1505.003 FIM adds of script files in web roots
Password spraying (low and slow) T1110.003 auth failures (rules 5710, 5716, 60122) by source across ≥ 10 users over 7d; composite rules may never fire

Read the full file on GitHub · 84 lines

Changes

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.

  1. yesterday First seen · 84 lines · 54 tokens per session scan A 84fe81135d1c

Subscribe to this mod's changes

threat-hunting is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (57 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 1,164 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.