What is deep-dive-ioc?

A workflow for investigating a potentially serious indicator of compromise, such as an IP address, domain, file hash, or web address linked to a security incident.

It helps gather threat-intelligence reports, search security logs, connect related entities, and record possible malware or attacker links for a case.

It provides a deeper investigation path when a basic lookup is not enough to understand whether an item is related to a threat.

deep-dive-ioc — Skill for Claude Code and Codex by dandye

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 dandye/ai-runbooks --skill deep-dive-ioc

Clone the repo

git clone --depth 1 https://github.com/dandye/ai-runbooks

Made for: Claude Code, Codex.

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/dandye/ai-runbooks/deep-dive-ioc/github.svg)](https://agentmods.dev/skills/dandye/ai-runbooks/deep-dive-ioc)

Your own site

<a href="https://agentmods.dev/skills/dandye/ai-runbooks/deep-dive-ioc"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/deep-dive-ioc/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/dandye/ai-runbooks/deep-dive-ioc"><img src="https://agentmods.dev/badge/skills/dandye/ai-runbooks/deep-dive-ioc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,097 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. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00057	$0.01097
Opus 5	$0.00028	$0.00549
Sonnet 5	$0.00011	$0.00219
Haiku 4.5	$0.00006	$0.00110

Measured 12d ago against content hash 3516bd8b0cd2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

deep-dive-ioc 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 12d 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.

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.

skills/deep-dive-ioc/SKILL.md · 139 lines

How it starts

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

Deep Dive IOC Analysis Skill

Perform exhaustive analysis of a single, potentially critical Indicator of Compromise escalated from Tier 1 or identified during an investigation.

Inputs

IOC_VALUE - The IOC to analyze (IP, domain, hash, or URL)
IOC_TYPE - The type: "IP Address", "Domain", "File Hash", or "URL"
CASE_ID - case ID for documentation (optional)
TIME_FRAME_HOURS - Lookback period (default: 168 = 7 days)

Workflow

Step 1: Get Case Context (if CASE_ID provided)

secops-soar.get_case_full_details(case_id=CASE_ID)

Step 2: Detailed GTI Report

Get comprehensive threat intelligence:

IOC Type	Tool
IP	`gti-mcp.get_ip_address_report(ip_address=IOC_VALUE)`
Domain	`gti-mcp.get_domain_report(domain=IOC_VALUE)`
Hash	`gti-mcp.get_file_report(hash=IOC_VALUE)`
URL	`gti-mcp.get_url_report(url=IOC_VALUE)`

Record:

Reputation and classifications
First/last seen dates
Associated threats (malware families, actors) → ASSOCIATED_THREAT_IDS
Key behaviors (for file hashes)

Step 3: GTI Pivoting

Use /pivot-on-ioc or directly call GTI relationship tools:

Recommended relationships by type:

IP: communicating_files, downloaded_files, resolutions
Domain: resolutions, communicating_files, subdomains
Hash: contacted_domains, contacted_ips, dropped_files
URL: communicating_files, downloaded_files

For file hashes, also get behavior summary:

gti-mcp.get_file_behavior_summary(hash=IOC_VALUE)

Step 4: Deep SIEM Search

Search for activity involving the IOC and its related entities:

secops-mcp.search_security_events(
    text="UDM query for IOC_VALUE",
    hours_back=TIME_FRAME_HOURS
)

Identify OBSERVED_RELATED_IOCS - IOCs from GTI pivoting that actually appear in SIEM results.

Step 5: SIEM Enrichment & Correlation

For the IOC and each OBSERVED_RELATED_IOC:

Use /enrich-ioc for enrichment
Use /correlate-ioc for alert/case correlation
Use /find-relevant-case for broader case search

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

12d ago First seen · 139 lines · 57 tokens per session scan A 3516bd8b0cd2

Subscribe to this mod's changes

deep-dive-ioc is a skill published in the GitHub repository dandye/ai-runbooks (124 stars, last pushed 28d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,097 once invoked, about $0.0003 per session on Opus 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-08-30.

Security

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens