incident-response-forensics — Claude Code skill: breach investigation
incident-response-forensics — a skill for collecting and analyzing digital evidence during security incident investigations. Preserves proof without corruption, gathers ephemeral data, and constructs an attack timeline.
no license 254 installs updated 2026-08-26
npx skills add securityskills/skills --skill incident-response-forensics -a claude-codeWhat incident-response-forensics does
The skill defines the correct sequence for responding to a system compromise. Start with a memory snapshot, then create a disk image through a write-blocker or verified snapshot with SHA-256 hashing and chain-of-custody documentation, while simultaneously collecting network logs from firewalls and proxies. The core principle: investigate the live system only read-only beyond initial collection—deeper probing triggers attacker tooling.
Next comes volatile data in strict order: network connections and routing, running processes, logged-in sessions, command histories. On Windows, examine Shimcache, Prefetch, and Event logs for logon events and process creation; on Linux check /var/log/auth.log and .bash_history. In cloud environments, review CloudTrail and AssumeRole chains. Normalize all artifacts into a unified timeline anchored to the first compromise indicator, then expand forward (persistence, lateral movement) and backward (reconnaissance, delivery).
Output includes IOCs with context, attack narrative mapped to ATT&CK techniques with evidence references, and a root-cause hypothesis. Requires familiarity with tools like WinPMEM, LiME, and log analysis utilities.
What it helps with
- collect evidence from a compromised system without destroying it
- map the attack timeline from initial access through data exfiltration
- identify lateral movement and persistence mechanisms
- determine the initial compromise vector
- document chain of custody for incident reports
Example prompts for the agent
- What's the correct order to collect evidence from a breached Windows server?
- Build a timeline from a Linux disk image using logs and command history
- Find signs of lateral movement in Event logs across the network
How to install incident-response-forensics
1Skills CLI (Vercel)
npx skills add securityskills/skills --skill incident-response-forensics -a claude-code2Manually: put the files in place
~/.claude/skills/incident-response-forensics/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/incident-response-forensics/
1Skills CLI (Vercel)
npx skills add securityskills/skills --skill incident-response-forensics -a codex2Manually: put the files in place
.agents/skills/incident-response-forensics/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add securityskills/skills --skill incident-response-forensics -a cursor2Manually: put the files in place
.cursor/skills/incident-response-forensics/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install securityskills/skills forensics/incident-response-forensics/SKILL.md2Manually: put the files in place
.github/skills/incident-response-forensics/SKILL.md1Skills CLI (Vercel)
npx skills add securityskills/skills --skill incident-response-forensics -a gemini-cli2Platform CLI
gemini skills install https://github.com/securityskills/skills --path forensics/incident-response-forensicsManually: put the files in place
.devin/skills/incident-response-forensics/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add securityskills/skills --skill incident-response-forensics -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about incident-response-forensics
How do I install incident-response-forensics skill in Claude Code?
Run npx skills add securityskills/skills --skill incident-response-forensics -a claude-code, then open ~/.claude/skills/incident-response-forensics/SKILL.md.
What does incident-response-forensics do?
It teaches a systematic approach to collecting and analyzing digital evidence: memory acquisition, disk imaging, log correlation, volatile data gathering in the proper sequence, and building a timeline of attacker actions from initial access to exfiltration.
Why should I avoid analyzing the live system directly?
Invasive investigation on a running system alerts the attacker's tooling to your presence. Read-only collection preserves evidence and maintains stealth during the investigation phase.