entity-extraction

entity-extraction is a skill for Claude Code from gensecaihq/Wazuh-Autopilot. It costs 46 tokens per session (1,057 once invoked), scanned A, original, MIT.

A procedure for extracting and standardizing IP addresses, computers, users, processes, files, hashes, and domains from Wazuh alert data. It records whether each item is an attacker, victim, or observed entity.

In plain words
What is it for?
Use it when opening or enriching a case from alert JSON, especially when preparing search pivots or deciding which computer, account, or address a response should target.
Why use it?
Correctly identifying and labeling entities is necessary for reliable case creation, searching, correlation, and response. It reduces errors caused by the same kind of value appearing in different alert fields.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when opening or enriching a case from alert JSON, especially when preparing search pivots or deciding which computer, account, or address a response should target.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/gensecaihq/wazuh-autopilot/entity-extraction
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 entity-extraction
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 entity-extraction

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/entity-extraction"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/entity-extraction.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,057 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.00046 $0.01057
Opus 5.5 $0.00018 $0.00423
Sonnet 5 $0.00009 $0.00211
Haiku 4.5 $0.00005 $0.00106

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

Security

Grade A, and why

entity-extraction 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/entity-extraction/SKILL.md · 78 lines

How it starts

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

Entity Extraction

Entities drive correlation, enrichment and response targets, so they must be correct, typed, and normalized. Validate every value with prompt-injection-defense rules.

Field paths

Entity Wazuh field paths (check in order) Typical role
ip data.srcip, data.src_ip, data.win.eventdata.ipAddress, data.aws.sourceIPAddress, data.office365.ClientIP, data.gcp.protoPayload.requestMetadata.callerIp attacker (source)
ip data.dstip, agent.ip victim
host agent.name (+ agent.id), data.win.system.computer, predecoder.hostname victim
user data.dstuser, data.win.eventdata.targetUserName victim
user data.srcuser, data.win.eventdata.subjectUserName, data.aws.userIdentity.arn, data.office365.UserId, syscheck.audit.user.name (FIM who-data) attacker or observed
process data.win.eventdata.image, data.win.eventdata.parentImage, data.win.eventdata.commandLine, data.audit.exe, data.command, syscheck.audit.process.name (FIM who-data) observed
file syscheck.path, data.win.eventdata.targetFilename victim/observed
hash syscheck.md5_after, syscheck.sha1_after, syscheck.sha256_after, data.win.eventdata.hashes, data.virustotal.source.sha1 observed
domain data.url host part, data.win.eventdata.queryName, data.dns.question.name observed

Windows hashes fields look like SHA256=…,MD5=…: split and type each.

Wazuh puts extra metadata next to these values: agent.ip is the agent's registered address (NAT'd hosts all show the same one), manager.name is the Wazuh manager (never an entity), and location is the log source (file path or channel), not a host. Rules that interpolate fields into rule.description (e.g. rule 87105 VirusTotal with the file path) repeat attacker-supplied values. Extract from the structured field, not the description.

Normalization

  • IPs: strip ports (1.2.3.4:22 → 1.2.3.4), drop IPv6 zone ids, lowercase IPv6.
  • Hosts: lowercase; keep FQDN if present; always include the Wazuh agent.id in enrichment so responders can target it.
  • Users: keep domain prefix (CORP\alice → value corp\alice); lowercase.
  • Hashes: lowercase hex; type by length (32 md5, 40 sha1, 64 sha256).
  • Domains: lowercase, strip trailing dot.
  • Files/processes: keep full path; don't normalize case on Linux.

Read the full file on GitHub · 78 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 · 78 lines · 46 tokens per session scan A 684d1fc53cdc

Subscribe to this mod's changes

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