agentleFS
saivarun3407saivarun3407/DFIR-AI/.claude/skills/threat-hunting/SKILL.md

threat-hunting

Skill0 starsChanged 6 months agoApache-2.0View on GitHub

Proactive ATT&CK-driven hunt across collected artifacts. Pivots from one finding to related TTPs via Diamond Model adversary/capability/infrastructure/victim graph. Pinned findings only.

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use web-pentest, malware-analysis and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • samklee1Skill

    web-pentest

    Orchestrates authorized web app pentesting on Kali Linux using Opus sub-agents with difficulty-aware planning (TDA/EGATS), browser-first exploration, iterative verification, two-layer review (per-sub-agent + phase-level), optional cross-model gap audit (GPT/codex via codex-plugin-cc), and enforced KB updates. Trigger on: pentesting, penetration testing, web app security assessment, vulnerability assessment, OWASP testing, PTES, attack surface mapping, API security testing, pentest reporting, or 'help me test this app'. NOT for network-only pentesting, malware analysis, reverse engineering, or CTFs.

    Also in 4 projects that use this

  • tsaleSkill

    malware-analysis

    Professional malware analysis workflow for PE executables and suspicious files. Triggers on file uploads with requests like "analyze this malware", "analyze this sample", "what does this executable do", "check this file for malware", or any request to examine suspicious files. Performs static analysis, threat intelligence triage, behavioral inference, and produces analyst-grade reports with reasoned conclusions.

    Also in 4 projects that use this

  • testified-ossSkill

    incident-triage

    Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.

    Also in 3 projects that use this

  • QiuChenlySkill

    reverse-engineering

    专业二进制逆向工程分析技能。使用IDA Pro MCP工具分析二进制文件、反编译代码、识别漏洞、理解程序逻辑。当用户要求分析可执行文件、反汇编、逆向工程、漏洞挖掘、恶意软件分析时使用此技能。

    Also in 4 projects that use this

  • msewellSkill

    threat-modeling

    Produces structured threat models for software systems using STRIDE on data flow diagrams. Generates DFDs with trust boundaries, identifies threats per element, scores risks, and defines concrete mitigations. Outputs a complete threat model Markdown document through phased, interactive delivery. Use when threat modeling a system, analyzing security threats, identifying attack surfaces, performing STRIDE analysis, assessing security risks in architecture, creating a threat model document, or when the user mentions threat model, attack surface, trust boundaries, STRIDE, or security risk analysis.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read state["_findings"] and state["attack_techniques"].

    line 16

“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Threat Hunting

You hunt for additional indicators given an initial finding set. Pivot via:

  1. MITRE ATT&CK — given a technique ID T####, look for sibling techniques used by the same adversary or in the same kill-chain stage.
  2. Diamond Model — given a vertex (adversary | capability | infrastructure | victim), traverse pivot_candidates(state, vertex) to surface adjacent indicators.
  3. Lockheed Kill Chain — given an observed stage, look for evidence of upstream/downstream stages that may have been missed.

Workflow

  1. Read state["_findings"] and state["attack_techniques"].
  2. For each technique, query MCP forensic primitives for adjacent artifacts.
  3. For each Diamond vertex, traverse outgoing relations.
  4. Emit new findings with full pins. Confidence inferred or uncertain only — confirmed requires ≥2 independent artifacts.
  5. Refuse to assert without pins. Use gap-acknowledgment skill when evidence is absent.

Output

New findings appended to _findings via finding_record MCP tool. Each must include:

  • claim
  • confidence (NEVER confirmed from hunt alone — needs corroboration)
  • pins (≥1)
  • mitre_attck (technique IDs surfaced)
  • related_findings (the parent finding_id that seeded the hunt)

Sub-Plan Status

Skeleton stub (Sub-Plan 03). Full Diamond traversal + pivot heuristics in Sub-Plan 04 (D3FEND integration).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.