Kubernetes Network Security Audit
kubeshark/kubeshark
Hunts for compromised workloads and malicious traffic in a Kubernetes cluster by sweeping network data through Kubeshark MCP, mapped to MITRE ATT&CK.
Respond to a ransomware incident following PICERL methodology.
Install Respond Ransomware
$ npx skills add dandye/ai-runbooks --skill respond-ransomware -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install dandye/ai-runbooks respond-ransomware --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/respond-ransomware .claude/skills/respond-ransomware && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "respond-ransomware" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomware into .claude/skills/respond-ransomware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-ransomware", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomwareType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add dandye/ai-runbooks --skill respond-ransomware -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install dandye/ai-runbooks respond-ransomware --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/respond-ransomware .agents/skills/respond-ransomware && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "respond-ransomware" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomware into .agents/skills/respond-ransomware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-ransomware", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dandye/ai-runbooks --skill respond-ransomware -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install dandye/ai-runbooks respond-ransomware --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/respond-ransomware .cursor/skills/respond-ransomware && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "respond-ransomware" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomware into .cursor/skills/respond-ransomware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-ransomware", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/dandye/ai-runbooks.git --path skills/respond-ransomware--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add dandye/ai-runbooks --skill respond-ransomware -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install dandye/ai-runbooks respond-ransomware --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/respond-ransomware .gemini/skills/respond-ransomware && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "respond-ransomware" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomware into .gemini/skills/respond-ransomware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-ransomware", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install dandye/ai-runbooks respond-ransomwareInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add dandye/ai-runbooks --skill respond-ransomware -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/respond-ransomware .github/skills/respond-ransomware && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "respond-ransomware" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomware into .github/skills/respond-ransomware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-ransomware", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add dandye/ai-runbooks --skill respond-ransomware -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install dandye/ai-runbooks respond-ransomware --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/dandye/ai-runbooks.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/respond-ransomware .opencode/skills/respond-ransomware && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "respond-ransomware" agent skill from https://github.com/dandye/ai-runbooks/tree/main/skills/respond-ransomware into .opencode/skills/respond-ransomware/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "respond-ransomware", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
respond-ransomware- GitHub stars
- 127
- Token cost
- ~1.7k tokens
- SKILL.md length
- 586 words
- Files
- 1
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Respond to a ransomware incident following PICERL methodology.
- Works in 6 steps: Preparation (Ongoing) → Identification → Containment → …
- Ransomware is detected
- SKILL.md covers Inputs, Required Outputs, PICERL Phases and Critical Warnings, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Respond Ransomware is an agent skill from dandye/ai-runbooks. Respond to a ransomware incident following PICERL methodology. Use when ransomware is detected or suspected. Orchestrates identification, containment, eradication, and recovery phases. Requires CASEID and initial indicators.
Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Security, covering Security operations. The licence is Apache-2.0.
When your agent uses it
- Ransomware is detected
- Tasks that involve Security operations
Example prompts
- “/respond-ransomware”
Workflow steps
6 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 72a6863. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Respond Ransomware loads about 1.7k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 586 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from dandye/ai-runbooks at commit 72a6863, republished under its Apache-2.0 licence (© dandye). 586 words, ~1,654 tokens.
Download SKILL.mdSave it as
.claude/skills/respond-ransomware/SKILL.md (or your agent's skills folder).- name
- respond-ransomware
- description
- Respond to a ransomware incident following PICERL methodology. Use when ransomware is detected or suspected. Orchestrates identification, containment, eradication, and recovery phases. Requires CASE_ID and initial indicators.
- type
- Skill
- required_roles.chronicle
- roles/chronicle.admin
- required_roles.soar
- roles/chronicle.soarAdmin
- required_roles.gti
- GTI Enterprise
- required_roles.scc
- roles/securitycenter.adminEditor
- personas
- incident-responder
- generated.by
- human:dandye
- generated.at
- 2026-02-04T06:10:49-05:00
Ransomware Incident Response Skill
Structured workflow for responding to suspected ransomware incidents using the PICERL model.
Inputs
CASE_ID- SOAR case ID for the incidentALERT_GROUP_IDENTIFIERS- Alert group identifiers from SOARINITIAL_INDICATORS- Initial detection info:- Affected endpoint(s)
- File hashes observed
- Ransom note details (handle carefully)
- Suspicious network connections
Required Outputs
After completing each phase, you MUST report these outputs:
Identification Phase
| Output | Description |
|---|---|
AFFECTED_SYSTEMS | Systems confirmed infected with ransomware |
RANSOMWARE_VARIANT | Ransomware family/variant identified |
ENCRYPTION_STATUS | Current encryption state of affected systems |
RANSOMWARE_IOCS | File hashes, ransom note patterns, malicious files |
Containment Phase
| Output | Description |
|---|---|
ISOLATED_SYSTEMS | Systems successfully isolated from network |
BLOCKED_IOCS | IOCs blocked at firewall/proxy |
C2_INDICATORS | C2 domains/IPs discovered during containment |
Eradication Phase
| Output | Description |
|---|---|
CLEANED_SYSTEMS | Systems with malware/persistence removed |
REMOVED_PERSISTENCE | Persistence mechanisms identified and removed |
Recovery Phase
| Output | Description |
|---|---|
RESTORED_SYSTEMS | Systems restored to operational state |
VALIDATION_STATUS | Post-recovery validation results |
PICERL Phases
Phase 1: Preparation (Ongoing)
Prerequisites - verify before proceeding:
- Tool connectivity (SIEM, SOAR, GTI, EDR)
- Backup availability and status
- Communication/escalation plans
Phase 2: Identification
Step 2.1: Get Context
secops-soar.get_case_full_details(case_id=CASE_ID)Use /check-duplicates to verify this isn't already under investigation.
Step 2.2: Identify Ransomware Strain
If file hash available:
gti-mcp.get_file_report(hash=FILE_HASH)If name/family known:
gti-mcp.search_threats(query="LockBit ransomware", collection_type="malware-family")Document: IDENTIFIED_STRAIN
Step 2.3: Investigate Initial Access & Lateral Movement
Search SIEM for activity BEFORE encryption:
secops-mcp.search_security_events(
text="Suspicious logins, RDP, exploit attempts for affected endpoints",
hours_back=168
)Look for:
- Suspicious logins to affected endpoints
- Lateral movement tools (PsExec, Cobalt Strike)
- Credential dumping activity
- Network connections from affected endpoints
Identify: INITIAL_ACCESS_VECTOR, POTENTIAL_ADDITIONAL_SYSTEMS
Step 2.4: Initial Scope Assessment
Compile:
AFFECTED_ENDPOINTS- Confirmed infected systemsMALICIOUS_IOCs- Network IOCs (C2 domains/IPs)
Step 2.5: Check Related Cases
Use /find-relevant-case with affected entities.
Step 2.6: Document
Use /document-in-case with identification findings.
Phase 3: Containment
CRITICAL: Speed is essential. Contain first, investigate deeper later.
Step 3.1: Isolate Affected Endpoints
For each endpoint in AFFECTED_ENDPOINTS and POTENTIAL_ADDITIONAL_SYSTEMS:
Use /confirm-action:
"Isolate endpoint [HOSTNAME] from network?"
If confirmed, trigger endpoint isolation (via EDR or network).
Step 3.2: Block Network IOCs
For each IOC in MALICIOUS_IOCs:
Use /confirm-action:
"Block IOC [VALUE] at firewall/proxy?"
If confirmed, implement blocks.
Step 3.3: Contain User Accounts
If compromised user identified:
→ Trigger /respond-compromised-account
Step 3.4: Verify Containment
Monitor SIEM for continued activity:
secops-mcp.search_security_events(
text="Activity from contained systems or IOCs",
hours_back=1
)Use /document-in-case with containment status.
Show full SKILL.md (241 more words)Show less
Phase 4: Eradication
Step 4.1: Identify Persistence
Review GTI reports for known persistence TTPs of IDENTIFIED_STRAIN.
Common mechanisms:
- Scheduled tasks
- Services
- Registry run keys
- WMI subscriptions
Step 4.2: Remove Malware & Persistence
(Requires EDR/endpoint tools)
- Remove ransomware executables
- Delete persistence mechanisms
- Note: Re-imaging often preferred over cleaning
Step 4.3: Scan Systems
Perform thorough AV/EDR scans on affected systems.
Use /document-in-case with eradication actions.
Phase 5: Recovery
Step 5.1: Check Decryptor Availability
Based on IDENTIFIED_STRAIN, check:
- NoMoreRansom.org
- Security vendor decryptor tools
Step 5.2: Determine Recovery Strategy
Options:
- Restore from clean backups (most common)
- Use decryptor if available
- Rebuild systems from scratch
Step 5.3: Execute Recovery
(Involves IT Ops/System Admins)
- Rebuild/restore systems
- Verify backup integrity before restore
- Patch and harden before reconnecting
- Restore data from clean backups
Step 5.4: Monitor & Lift Containment
- Monitor recovered systems closely
- Gradually remove isolation measures
- Watch for signs of residual infection
Use /document-in-case with recovery status.
Phase 6: Lessons Learned
Use /generate-report with comprehensive incident report.
Conduct post-incident review:
- Initial access vector analysis
- Detection timeline review
- Response effectiveness
- Recovery success
- Recommendations for prevention
Critical Warnings
- DO NOT delay containment to perform deep analysis
- DO NOT restore without verifying backups/cleaning
- DO check for lateral movement before closing
- ALWAYS confirm isolation actions with analyst
Quick Reference
| Phase | Key Actions | Skills Used |
|---|---|---|
| Identification | Strain ID, scope | /check-duplicates, /find-relevant-case |
| Containment | Isolate, block | /confirm-action, /document-in-case |
| Eradication | Remove persistence | EDR tools |
| Recovery | Restore systems | IT Ops coordination |
| Lessons Learned | Report, review | /generate-report |
© dandye, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/respond-ransomware of dandye/ai-runbooks.
Open the folder on GitHubat commit 72a6863
Compare with similar skills
Respond Ransomware next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Respond Ransomware this skilldandye/ai-runbooks | 127 | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Kubernetes Network Security Auditkubeshark/kubeshark | 12k | — | ~7.3k | Automated safety check: Notes | Apache-2.0 | |
| DefectDojo Vulnerability ManagementAgentSecOps/SecOpsAgentKit | 220 | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Ecs Operation Reviewaws/tools-for-devops-agent | 103 | — | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Deploying Osquery For Endpoint Monitoringmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| Hunting For Webshell Activitymukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~904 | Automated safety check: Pass | Apache-2.0 |
Similar skills
DefectDojo Vulnerability Management
AgentSecOps/SecOpsAgentKit
Aggregates scanner results into DefectDojo, deduplicates findings, tracks remediation SLAs and prepares compliance reports across products and pipelines.
- Official
Ecs Operation Review
aws/tools-for-devops-agent
Performs a comprehensive Amazon ECS operations review across the 6 review pillars (Resiliency & HA, Observability, Security, Operations, Performance, Additional Analysis) using read-only AWS APIs…
Deploying Osquery For Endpoint Monitoring
mukul975/Anthropic-Cybersecurity-Skills
Deploys and configures osquery for real-time endpoint monitoring using SQL-based queries to inspect running processes, open ports, installed software, and system configuration.
Hunting For Webshell Activity
mukul975/Anthropic-Cybersecurity-Skills
Runs a hypothesis-driven threat hunt for web shell deployment (T1505.003) on internet-facing servers by analyzing file creation in web directories, suspicious child-process spawning from web server…
Detecting Network Anomalies With Zeek
mukul975/Anthropic-Cybersecurity-Skills
Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection/DNS/HTTP/SSL/file logs, detect anomalous behavior, and write custom scripts for…
More from dandye/ai-runbooks
All 27 skills in this repoClose Case Artifact
dandye/ai-runbooks
Close a case or alert with proper reason and documentation. An agent skill from dandye/ai-runbooks.
Correlate Ioc
dandye/ai-runbooks
Check for existing SIEM alerts and case management entries related to IOCs.
Deep Dive Ioc
dandye/ai-runbooks
Perform exhaustive analysis of a critical IOC. An agent skill from dandye/ai-runbooks.
Enrich Ioc
dandye/ai-runbooks
Enrich an IOC (IP, domain, hash, URL) with threat intelligence.
Find Relevant Case
dandye/ai-runbooks
Search for existing cases related to specific indicators or entities.
Full Alert Triage
dandye/ai-runbooks
Complete Tier 1 triage workflow. An agent skill from dandye/ai-runbooks.
Related
Categories
Questions about Respond Ransomware
What does Respond Ransomware do?
Respond to a ransomware incident following PICERL methodology. Respond Ransomware is an agent skill from dandye/ai-runbooks. Respond to a ransomware incident following PICERL methodology.
When should I use Respond Ransomware?
Respond Ransomware fits situations like: ransomware is detected; tasks that involve Security operations.
How do I install Respond Ransomware in Claude Code?
Run `npx skills add dandye/ai-runbooks --skill respond-ransomware -a claude-code`. Or copy the skill folder (skills/respond-ransomware in dandye/ai-runbooks) into .claude/skills/respond-ransomware in your project. Claude Code loads it when a task matches its description.
How do I install Respond Ransomware in Codex?
Run `npx skills add dandye/ai-runbooks --skill respond-ransomware -a codex`. Or copy the skill folder (skills/respond-ransomware in dandye/ai-runbooks) into .agents/skills/respond-ransomware in your project. Codex loads it when a task matches its description.
Can I use Respond Ransomware in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dandye/ai-runbooks --skill respond-ransomware -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/respond-ransomware, .gemini/skills/respond-ransomware, .github/skills/respond-ransomware and .opencode/skills/respond-ransomware in your project.
What does Respond Ransomware need to run?
SKILL.md names no scripts, command-line tools or credentials: Respond Ransomware is instructions for the agent only.
Does Respond Ransomware access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Respond Ransomware safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Respond Ransomware use?
Respond Ransomware is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Respond Ransomware use?
About 1.7k tokens (SKILL.md is roughly 6.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Respond Ransomware?
Skills that share tags, products or a category with Respond Ransomware: Kubernetes Network Security Audit (kubeshark/kubeshark, 12k stars), DefectDojo Vulnerability Management (AgentSecOps/SecOpsAgentKit, 220 stars), Ecs Operation Review (aws/tools-for-devops-agent, 103 stars) and Deploying Osquery For Endpoint Monitoring (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Respond Ransomware?
dandye (a GitHub user) maintains it in dandye/ai-runbooks, which has 127 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on August 14, 2026.
Source: dandye/ai-runbooks on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.