Agent skill · security · jeremylongshore
responding-to-security-incidents
Analyze and guide security incident response, investigation, and remediation
Why this skill is useful
Adds detailed incident response playbooks and executable forensic commands that enhance the AI's capability to manage security incidents.
What it needs
Requires autopsy, tcpdump, volatility, wireshark installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Responding To Security Incidents Overview Guide the full NIST SP 800-61 incident response lifecycle: detection, containment, eradication, recovery, and post-incident analysis. Classify incidents by type (ransomware, data breach, DDoS, credential compromise, insider threat) and severity, then coordinate evidence preservation, threat containment, and root-cause investigation. Prerequisites System and application logs accessible in ${CLAUDESKILLDIR}/logs/ (auth logs, web server logs, database access logs) Network traffic captures (PCAP) or SIEM alert exports available Incident response team contact information and escalation paths documented Backup systems operational and recovery procedures tested Write permissions for incident documentation in ${CLAUDESKILLDIR}/incidents/ Forensic tools available: Volatility (memory), Autopsy/FTK Imager (disk), tcpdump/Wireshark (network) Instructions 1. Classify the incident: determine type (ransomware, data breach, DDoS, phishing, insider threat), assign severity (Critical/High/Medium/Low), and record initial detection timestamp and method. 2. Scope affected systems: identify all compromised hosts, user accounts, data stores, and network segments. Map the blast radius. 3. Preserve evidence before any changes: capture memory dumps (volatility -f memdump.raw imageinfo), create disk images, export running process lists (ps auxf), and snapshot network connection state (ss -tulnp). 4. Collect log evidence: gather authentication logs (successful and failed), application error logs, firewall/IDS alerts, DNS query logs, and proxy server logs. Store originals in ${CLAUDESKILLDIR}/incidents/evidence/. 5. Contain the threat: isolate affected systems from the network, disable compromised accounts, block malicious IPs at the firewall, and revoke compromised API keys or tokens. 6. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/responding-to-security-incidents--a62bdc