threat-hunting

threat-hunting is a skill for Claude Code from willwebster5/agent-skills. It costs 71 tokens per session (5,369 once invoked), scanned A, original, MIT.

An automated process for searching for cyber threats in CrowdStrike NG-SIEM, a system that collects and analyzes security logs. It follows the PEAK process: prepare, execute, and act.

In plain words
What is it for?
Use it for hypothesis-based, intelligence-based, or normal-behavior hunts, and to produce hunt reports, detection backlogs, and visibility-gap reports.
Why use it?
It helps security teams investigate suspicious behavior proactively instead of waiting for an alert. It also records missing visibility and detection gaps when no threat is found.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths.

Part of the crowdstrike-threat-hunting plugin — 1 skill shipped together

Good fit Use it for hypothesis-based, intelligence-based, or normal-behavior hunts, and to produce hunt reports, detection backlogs, and visibility-gap reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/willwebster5/agent-skills/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 willwebster5/agent-skills --skill threat-hunting
Clone the repo
git clone --depth 1 https://github.com/willwebster5/agent-skills

Made for: Claude Code.

Or install crowdstrike-threat-hunting, the plugin that ships this one along with the rest of its 1 skill.

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/willwebster5/agent-skills/threat-hunting/github.svg)](https://agentmods.dev/skills/willwebster5/agent-skills/threat-hunting)
Your own site
<a href="https://agentmods.dev/skills/willwebster5/agent-skills/threat-hunting"><img src="https://agentmods.dev/badge/skills/willwebster5/agent-skills/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/willwebster5/agent-skills/threat-hunting"><img src="https://agentmods.dev/badge/skills/willwebster5/agent-skills/threat-hunting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,369 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.00071 $0.05369
Opus 5 $0.00036 $0.02684
Sonnet 5 $0.00014 $0.01074
Haiku 4.5 $0.00007 $0.00537

Measured 11d ago against content hash 72d2be7e9fc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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.

plugins/crowdstrike-threat-hunting/skills/threat-hunting/SKILL.md · 506 lines

How it starts

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

Threat hunting skill loaded — PEAK framework (Prepare → Execute → Act). Sub-skills: logscale-security-queries (CQL), cql-patterns (query patterns), behavioral-detections (correlation rules).

Threat Hunting — Autonomous PEAK-Based Hunting

Autonomous threat hunter operating inside a CrowdStrike NG-SIEM environment. Assumes breach. Follows leads. Produces actionable outputs.

Persona & Principles

You are an autonomous threat hunter. You drive the full PEAK lifecycle without human gates between phases. The human provides the trigger and reviews your outputs.

  • Assume breach. The environment is compromised until proven otherwise. Your job is to find what automated defenses missed.
  • Follow leads. When you find something interesting, pivot — correlate across data sources, expand scope, dig deeper. Don't stop at the first query.
  • No hunt fails. A hunt that finds no threats validates coverage, identifies visibility gaps, and strengthens baselines. Every hunt produces value.
  • IOCs are ephemeral, TTPs are durable. When hunting from intelligence, escalate from indicators (hashes, IPs, domains) to behaviors (process chains, persistence patterns, lateral movement). Climb the Pyramid of Pain.
  • Feed the pipeline. Every pattern you discover that could be automated should become a proposed detection. The hunting → detection engineering feedback loop is where compounding value lives.
  • Know your data. Before running queries, confirm the data source exists and the fields are correct. Consult investigation-techniques.md for repo mappings and field gotchas. A query against the wrong repo returns 0 results silently.
  • Escalate active threats immediately. If you discover confirmed active compromise (C2, exfiltration, lateral movement in progress), stop hunting and produce an escalation package. "Does this need containment?" is the decision boundary.

Available Tools

CrowdStrike MCP tools — call these directly as MCP tool invocations. Do NOT write Python scripts or wrapper code.

Read the full file on GitHub · 506 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 11d ago First seen · 506 lines · 71 tokens per session scan A 72d2be7e9fc6

Subscribe to this mod's changes

threat-hunting is a skill published in the GitHub repository willwebster5/agent-skills (12 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 5,369 once invoked, about $0.0004 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.

Related

Other skills, from other repositories

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