Use it to investigate added, modified or deleted files and registry entries, review checksums and permissions, and connect changes to users or processes.

It helps distinguish routine changes from tampering or persistence. It also highlights when Wazuh may have missed changes because its monitoring queue or file limit was full.

wazuh-fim-investigation — Skill for Claude Code by gensecaihq

Q: What is wazuh-fim-investigation?

A guide for investigating Wazuh File Integrity Monitoring alerts, which report changes to monitored files and Windows registry entries. It compares the change with expected activity such as patching or configuration updates.

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 wazuh-fim-investigation

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-fim-investigation/github.svg)](https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/wazuh-fim-investigation)

Your own site

<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/wazuh-fim-investigation"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-fim-investigation/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gensecaihq/wazuh-autopilot/wazuh-fim-investigation"><img src="https://agentmods.dev/badge/skills/gensecaihq/wazuh-autopilot/wazuh-fim-investigation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 65 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,648 The whole file, excluding the scripts and references it only reads on demand.

Security scan D 2 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.

Model	Per session	Once invoked
Fable 5.1	$0.00065	$0.01648
Opus 5.5	$0.00026	$0.00659
Sonnet 5.5	$0.00013	$0.00330
Haiku 4.5	$0.00006	$0.00165

Measured 1mo ago against content hash 27930f5b6452, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade D, and why

wazuh-fim-investigation scanned grade D with 2 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 1mo ago.

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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

4. **Who did it**: use who-data if present; otherwise look for logins/sudo on the agent around the change

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

| `/root/.ssh/authorized_keys`, `~/.ssh/authorized_keys` | Persistence via keys (T1098.004) |

backend/app/skills/wazuh-fim-investigation/SKILL.md · 100 lines

How it starts

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

Wazuh FIM Investigation

Wazuh FIM (syscheck) alerts on changes to monitored files and Windows registry entries. The question is always: expected change (patching, config management) or tampering/persistence?

Core syscheck rules (stock ruleset)

Event	Files	Windows registry key	Windows registry value
Modified	rule 550 (level 7)	rule 594 (level 5)	rule 750 (level 5)
Deleted	rule 553 (level 7)	rule 597 (level 5)	rule 751 (level 5)
Added	rule 554 (level 5)	rule 598 (level 5)	rule 752 (level 5)

Groups: syscheck, plus syscheck_entry_modified / syscheck_entry_deleted / syscheck_entry_added and syscheck_file / syscheck_registry. Query by group: get_wazuh_alerts rule_groups=["syscheck"] agent_id="<id>" timestamp_start="now-24h".

FIM health signals (monitoring gaps, not attacks): rule 560 (level 7, "FIM real-time queue is full") and rule 233 (level 12, "The maximum limit of files monitored has been reached") mean changes may have been missed — record it and hand off to platform-engineer.

Key fields

Field	Use
`syscheck.path`	What changed
`syscheck.event`	added / modified / deleted
`syscheck.mode`	`realtime`, `whodata` or `scheduled` — scheduled scans only tell you the change happened since the last scan
`syscheck.md5_before/after`, `sha1_`, `sha256_`	Content change; hashes go to threat-intel for reputation
`syscheck.size_before/after`	Truncation, appended payloads
`syscheck.perm_before/after`, `uname_`, `gname_`, `uid_*`	Permission / ownership changes (e.g. SUID, world-writable)
`syscheck.changed_attributes`	Which attributes changed
`syscheck.diff`	Text diff (only when `report_changes` is enabled for the path)
`syscheck.audit.user.name`, `.audit.effective_user.name`, `.audit.process.name`, `.audit.process.id`, `.audit.process.ppid`	Who-data: which user and process made the change (Linux auditd / Windows SACL)

If syscheck.audit.* is absent the path isn't in who-data mode — you know what changed, not who. Say so rather than guessing.

Read the full file on GitHub · 100 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.

1mo ago First seen · 100 lines · 65 tokens per session scan D 27930f5b6452

Subscribe to this mod's changes

wazuh-fim-investigation is a skill published in the GitHub repository gensecaihq/Wazuh-Autopilot (63 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,648 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-25.

Autonomous Agents Debugging Security agentic-ai mcp security-automation siem soc

wazuh-fim-investigation next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
wazuh-fim-investigationgensecaihq/Wazuh-Autopilot	Skill	63	1mo ago	MIT	D	65	Claude Code
agent-performance-optimizerruvnet/ruflo	Skill	81k	today	MIT	A	19	Claude Code
agent-refinementruvnet/ruflo	Skill	81k	today	MIT	A	15	Claude Code
diag-harnessruvnet/metaharness	Skill	744	today	MIT	A	85	Claude Code
business-logic-and-state-abusemakifbaysal/tasktrooper	Skill	122	yesterday	Apache-2.0	A	82	Claude Code, Codex
root-cause-debuggingmakifbaysal/tasktrooper	Skill	122	yesterday	Apache-2.0	A	47	Claude Code, Codex
unity-performance-and-gcmakifbaysal/tasktrooper	Skill	122	yesterday	Apache-2.0	A	76	Claude Code, Codex

wazuh-fim-investigation