Security Alert Triage
elastic/agent-skills
Triage Elastic Security alerts — gather context, classify threats, create cases, and acknowledge.
Hunt for specific IOCs across your environment. An agent skill from dandye/ai-runbooks.
Install Hunt Ioc
$ npx skills add dandye/ai-runbooks --skill hunt-ioc -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dandye/ai-runbooks hunt-ioc --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/hunt-ioc .claude/skills/hunt-ioc && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "hunt-ioc" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-ioc into .claude/skills/hunt-ioc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunt-ioc", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-iocType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dandye/ai-runbooks --skill hunt-ioc -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dandye/ai-runbooks hunt-ioc --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/hunt-ioc .agents/skills/hunt-ioc && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "hunt-ioc" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-ioc into .agents/skills/hunt-ioc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunt-ioc", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dandye/ai-runbooks --skill hunt-ioc -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dandye/ai-runbooks hunt-ioc --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/hunt-ioc .cursor/skills/hunt-ioc && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "hunt-ioc" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-ioc into .cursor/skills/hunt-ioc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunt-ioc", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dandye/ai-runbooks.git --path skills/hunt-ioc--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dandye/ai-runbooks --skill hunt-ioc -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dandye/ai-runbooks hunt-ioc --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/hunt-ioc .gemini/skills/hunt-ioc && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "hunt-ioc" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-ioc into .gemini/skills/hunt-ioc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunt-ioc", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dandye/ai-runbooks hunt-iocInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dandye/ai-runbooks --skill hunt-ioc -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/hunt-ioc .github/skills/hunt-ioc && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "hunt-ioc" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-ioc into .github/skills/hunt-ioc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunt-ioc", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dandye/ai-runbooks --skill hunt-ioc -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dandye/ai-runbooks hunt-ioc --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/hunt-ioc .opencode/skills/hunt-ioc && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "hunt-ioc" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/hunt-ioc into .opencode/skills/hunt-ioc/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hunt-ioc", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
hunt-ioc- GitHub stars
- 127
- Token cost
- ~958 tokens
- SKILL.md length
- 284 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Hunt for specific IOCs across your environment. An agent skill from dandye/ai-runbooks.
- Works in 7 steps: Parse and Validate IOCs → Initial IOC Match Check → Iterative SIEM Search → …
- You have a list of IPs
- SKILL.md covers Inputs, Workflow, Output Summary Template and Required Outputs, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Hunt Ioc is an agent skill from dandye/ai-runbooks. Hunt for specific IOCs across your environment. Use when you have a list of IPs, domains, hashes, or URLs from threat intel and want to check if they appear in your SIEM. Systematic searching with enrichment and documentation.
Its SKILL.md is about 960 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Security operations. The licence is Apache-2.0.
When your agent uses it
- You have a list of IPs
- URLs from threat intel and want to check if they appear in your SIEM
Example prompts
- “/hunt-ioc”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 72a6863. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are udm and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hunt Ioc loads about 958 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 284 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dandye/ai-runbooks at commit 72a6863, republished under its Apache-2.0 licence (© dandye). 284 words, ~958 tokens.
Download SKILL.mdSave it as
.claude/skills/hunt-ioc/SKILL.md (or your agent's skills folder).- name
- hunt-ioc
- description
- Hunt for specific IOCs across your environment. Use when you have a list of IPs, domains, hashes, or URLs from threat intel and want to check if they appear in your SIEM. Systematic searching with enrichment and documentation.
- type
- Skill
- required_roles.chronicle
- roles/chronicle.editor
- required_roles.gti
- GTI Enterprise
- personas
- threat-hunter, tier2-analyst
- generated.by
- human:dandye
- generated.at
- 2026-02-04T06:10:49-05:00
IOC Threat Hunt Skill
Proactively hunt for specific Indicators of Compromise (IOCs) across the environment based on threat intelligence feeds, recent incidents, or emerging threats.
Inputs
IOC_LIST- Comma-separated list of IOC values to huntIOC_TYPES- Corresponding types (e.g., "IP Address, Domain, File Hash")HUNT_TIMEFRAME_HOURS- Lookback period (default: 96)- (Optional)
HUNT_CASE_ID- SOAR case for tracking - (Optional)
REASON_FOR_HUNT- Why these IOCs are being hunted
Workflow
Step 1: Parse and Validate IOCs
Parse IOC_LIST and IOC_TYPES into structured list.
Validate IOC formats (IP regex, hash length, etc.).
Step 2: Initial IOC Match Check
secops-mcp.get_ioc_matches(hours_back=HUNT_TIMEFRAME_HOURS)Check if any IOCs appear in integrated threat feeds.
Step 3: Iterative SIEM Search
For each IOC, construct appropriate UDM query:
IP Address:
(principal.ip = "IOC" OR target.ip = "IOC" OR network.ip = "IOC")Domain:
(principal.hostname = "IOC" OR target.hostname = "IOC" OR network.dns.questions.name = "IOC")File Hash:
(target.file.sha256 = "IOC" OR target.file.md5 = "IOC" OR target.file.sha1 = "IOC")URL:
target.url = "IOC"Execute each search:
secops-mcp.search_security_events(text=query, hours_back=HUNT_TIMEFRAME_HOURS)Step 4: Analyze Results
For each search result:
- Identify affected hosts, users, processes
- Note event types (login, network connection, file execution)
- Assess if activity is suspicious or expected
Step 5: Enrich Hits
If hits found for an IOC:
Use /enrich-ioc for the IOC itself.
For involved entities (hosts, users):
secops-mcp.lookup_entity(entity_value=ENTITY)Step 6: Document Hunt
Use /document-in-case (if HUNT_CASE_ID provided):
IOC Hunt Summary:
- IOCs Hunted: [list]
- Timeframe: [hours]
- Queries Used: [list with results summary]
- IOCs with Hits: [list with details]
- IOCs with No Hits: [list - confirms environment is clean]
- Enrichment: [for hits]
- Recommendations: [next steps]Step 7: Escalate or Conclude
Confirmed malicious activity: → Create/update incident case → Trigger appropriate response runbook
No significant findings: → Document hunt completion → Note clean IOCs for future reference
Output Summary Template
# IOC Hunt Results
**Hunt Date:** [timestamp]
**Timeframe:** Last [X] hours
**Reason:** [REASON_FOR_HUNT]
## IOCs Searched
| IOC | Type | Result | Notes |
|-----|------|--------|-------|
| 198.51.100.10 | IP | NO HITS | Clean |
| evil.com | Domain | 3 HITS | DNS lookups from HOST1 |
## Hits Analysis
[Details for each IOC with hits]
## Recommendations
[Actions to take]Required Outputs
After completing this skill, you MUST report these outputs:
| Output | Description |
|---|---|
MATCHES | IOCs found in SIEM (list of IOCs with hits) |
MATCH_CONTEXT | Context for each match (events, assets, users affected) |
MATCHES_FOUND | Boolean: true if any IOCs found in environment, false otherwise |
Critical Requirements
- Search ALL provided IOCs (don't skip any)
- Use correct timeframe (not 1 hour instead of 72)
- Document negative results (confirms environment is clean)
- Don't declare "clean" if there were obvious hits
© dandye, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/hunt-ioc of dandye/ai-runbooks.
Open the folder on GitHubat commit 72a6863
Compare with similar skills
Hunt Ioc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Hunt Ioc this skilldandye/ai-runbooks | 127 | — | ~958 | Automated safety check: Pass | Apache-2.0 | |
| Security Alert Triageelastic/agent-skills | 592 | 1 repos | ~3.5k | Automated safety check: Notes | Apache-2.0 | |
| Kubernetes Network Security Auditkubeshark/kubeshark | 12k | — | ~7.3k | Automated safety check: Notes | Apache-2.0 | |
| Security Detection Rule Managementelastic/agent-skills | 592 | 1 repos | ~3.9k | Automated safety check: Notes | Apache-2.0 | |
| Chaitin CLIchaitin/chaitin-cli | 115 | — | ~15k | Automated safety check: Notes | GPL-3.0 | |
| GatesNebulock-Inc/agentic-threat-hunting-framework | 388 | — | ~12k | Automated safety check: Pass | MIT |
Similar skills
- Official
Kubernetes Network Security Audit
kubeshark/kubeshark
Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.
- Official
Security Detection Rule Management
elastic/agent-skills
Create, tune, and manage Elastic Security detection rules (SIEM and Endpoint).
Chaitin CLI
chaitin/chaitin-cli
A skill your agent uses when running chaitin-cli commands to manage Chaitin security products: SafeLine WAF (site management, IP blocking, ACL, policy rules, attack logs), X-Ray vulnerability…
Gates
Nebulock-Inc/agentic-threat-hunting-framework
GATES method validation for hunt-derived detections. An agent skill from Nebulock-Inc/agentic-threat-hunting-framework.
Elasticsearch Audit
aspectrr/deer
Enable, configure, and query Elasticsearch security audit logs.
More from dandye/ai-runbooks
All 27 skills in this repoClose Case Artifact
dandye/ai-runbooks
Close a case or alert with proper reason and documentation. An agent skill from dandye/ai-runbooks.
Correlate Ioc
dandye/ai-runbooks
Check for existing SIEM alerts and case management entries related to IOCs.
Deep Dive Ioc
dandye/ai-runbooks
Perform exhaustive analysis of a critical IOC. An agent skill from dandye/ai-runbooks.
Enrich Ioc
dandye/ai-runbooks
Enrich an IOC (IP, domain, hash, URL) with threat intelligence.
Find Relevant Case
dandye/ai-runbooks
Search for existing cases related to specific indicators or entities.
Full Alert Triage
dandye/ai-runbooks
Complete Tier 1 triage workflow. An agent skill from dandye/ai-runbooks.
Related
Categories
Questions about Hunt Ioc
What does Hunt Ioc do?
Hunt for specific IOCs across your environment. An agent skill from dandye/ai-runbooks. Hunt Ioc is an agent skill from dandye/ai-runbooks. Hunt for specific IOCs across your environment.
When should I use Hunt Ioc?
Hunt Ioc fits situations like: you have a list of IPs; URLs from threat intel and want to check if they appear in your SIEM.
How do I install Hunt Ioc in Claude Code?
Run `npx skills add dandye/ai-runbooks --skill hunt-ioc -a claude-code`. Or copy the skill folder (skills/hunt-ioc in dandye/ai-runbooks) into .claude/skills/hunt-ioc in your project. Claude Code loads it when a task matches its description.
How do I install Hunt Ioc in Codex?
Run `npx skills add dandye/ai-runbooks --skill hunt-ioc -a codex`. Or copy the skill folder (skills/hunt-ioc in dandye/ai-runbooks) into .agents/skills/hunt-ioc in your project. Codex loads it when a task matches its description.
Can I use Hunt Ioc in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dandye/ai-runbooks --skill hunt-ioc -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hunt-ioc, .gemini/skills/hunt-ioc, .github/skills/hunt-ioc and .opencode/skills/hunt-ioc in your project.
What does Hunt Ioc need to run?
SKILL.md names no scripts, command-line tools or credentials: Hunt Ioc is instructions for the agent only.
Does Hunt Ioc access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Hunt Ioc safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Hunt Ioc use?
Hunt Ioc is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hunt Ioc use?
About 958 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Hunt Ioc?
Skills that share tags, products or a category with Hunt Ioc: Security Alert Triage (elastic/agent-skills, 592 stars), Kubernetes Network Security Audit (kubeshark/kubeshark, 12k stars), Security Detection Rule Management (elastic/agent-skills, 592 stars) and Chaitin CLI (chaitin/chaitin-cli, 115 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hunt Ioc?
dandye (a GitHub user) maintains it in dandye/ai-runbooks, which has 127 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on August 14, 2026.
Source: dandye/ai-runbooks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.