Storage S3 Resiliency Expertise
aws/tools-for-devops-agent
S3 resiliency, security, and data protection review. An agent skill from aws/tools-for-devops-agent.
Agent skill
Testing Ransomware Recovery Procedures
Tests and validates ransomware recovery procedures - backup restore operations (e.g.
Install Testing Ransomware Recovery Procedures
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills testing-ransomware-recovery-procedures --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/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/testing-ransomware-recovery-procedures .claude/skills/testing-ransomware-recovery-procedures && 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 "testing-ransomware-recovery-procedures" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-procedures into .claude/skills/testing-ransomware-recovery-procedures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ransomware-recovery-procedures", 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/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-proceduresType 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 mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills testing-ransomware-recovery-procedures --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/testing-ransomware-recovery-procedures .agents/skills/testing-ransomware-recovery-procedures && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "testing-ransomware-recovery-procedures" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-procedures into .agents/skills/testing-ransomware-recovery-procedures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ransomware-recovery-procedures", 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 mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills testing-ransomware-recovery-procedures --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/testing-ransomware-recovery-procedures .cursor/skills/testing-ransomware-recovery-procedures && 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 "testing-ransomware-recovery-procedures" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-procedures into .cursor/skills/testing-ransomware-recovery-procedures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ransomware-recovery-procedures", 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/mukul975/Anthropic-Cybersecurity-Skills.git --path skills/testing-ransomware-recovery-procedures--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 mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills testing-ransomware-recovery-procedures --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/testing-ransomware-recovery-procedures .gemini/skills/testing-ransomware-recovery-procedures && 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 "testing-ransomware-recovery-procedures" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-procedures into .gemini/skills/testing-ransomware-recovery-procedures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ransomware-recovery-procedures", 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 mukul975/Anthropic-Cybersecurity-Skills testing-ransomware-recovery-proceduresInstalls 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 mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/testing-ransomware-recovery-procedures .github/skills/testing-ransomware-recovery-procedures && 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 "testing-ransomware-recovery-procedures" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-procedures into .github/skills/testing-ransomware-recovery-procedures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ransomware-recovery-procedures", 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 mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mukul975/Anthropic-Cybersecurity-Skills testing-ransomware-recovery-procedures --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mukul975/Anthropic-Cybersecurity-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/testing-ransomware-recovery-procedures .opencode/skills/testing-ransomware-recovery-procedures && 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 "testing-ransomware-recovery-procedures" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/testing-ransomware-recovery-procedures into .opencode/skills/testing-ransomware-recovery-procedures/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "testing-ransomware-recovery-procedures", 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
testing-ransomware-recovery-procedures- GitHub stars
- 34k
- Token cost
- ~1.9k tokens
- SKILL.md length
- 606 words
- Files
- 4 (incl. scripts, references)
- Skills in repo
- 644
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Tests and validates ransomware recovery procedures - backup restore operations (e.g.
- Works in 6 steps: Define Recovery Test Scope → Prepare Test Environment → Execute Restore and Measure RTO → …
- Validating that recovery plans work under realistic conditions
- SKILL.md covers When to Use, Prerequisites, Workflow and Key Concepts, plus 3 more sections
- Runs Python scripts from its folder; calls psql
What it does
Testing Ransomware Recovery Procedures is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Tests and validates ransomware recovery procedures - backup restore operations (e.g. with Restic), RTO/RPO target verification, recovery sequencing, and clean-restore validation - to confirm organizational resilience against destructive ransomware attacks. Use when validating that recovery plans work under realistic conditions, measuring RTO/RPO against business requirements, or testing restore integrity after simulated encryption.
Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including scripts and reference files (for example `references/api-reference.md` and `scripts/agent.py`).
It sits in DevOps & Cloud, covering Backup and disaster recovery and PRD writing. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
- Validating that recovery plans work under realistic conditions
- Measuring RTO/RPO against business requirements
- Testing restore integrity after simulated encryption
Example prompts
- “Use the testing-ransomware-recovery-procedures skill to test and validates ransomware recovery procedures - backup restore operations (e.g”
- “/testing-ransomware-recovery-procedures”
Requirements
- Python 3
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 54a7988. 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
Ships 1 file in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
psql
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
cisa.govveeam.com
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
Testing Ransomware Recovery Procedures loads about 1.9k tokens when it runs, and up to ~2.9k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 606 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); the scripts in this folder are not scanned.
SKILL.md
The full file from mukul975/Anthropic-Cybersecurity-Skills at commit 54a7988, republished under its Apache-2.0 licence (© mukul975). 606 words, ~1,946 tokens.
Download SKILL.mdSave it as
.claude/skills/testing-ransomware-recovery-procedures/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- testing-ransomware-recovery-procedures
- description
- Tests and validates ransomware recovery procedures - backup restore operations (e.g. with Restic), RTO/RPO target verification, recovery sequencing, and clean-restore validation - to confirm organizational resilience against destructive ransomware attacks. Use when validating that recovery plans work under realistic conditions, measuring RTO/RPO against business requirements, or testing restore integrity after simulated encryption.
- domain
- cybersecurity
- subdomain
- incident-response
- tags
- incident-response, ransomware, disaster-recovery, backup, rto, rpo, resilience
- version
- 1.0
- author
- mahipal
- license
- Apache-2.0
- nist_csf
- RS.MA-01, RS.MA-02, RS.AN-03, RC.RP-01
- mitre_attack
- T1486, T1490, T1070, T1078, T1489
- mitre_f3.version
- 1.1
- mitre_f3.tactics
- positioning, monetization
Testing Ransomware Recovery Procedures
When to Use
Use this skill when:
- Validating that ransomware recovery plans actually work under realistic conditions
- Measuring RTO (Recovery Time Objective) and RPO (Recovery Point Objective) against business requirements
- Testing backup restore operations to confirm data integrity and completeness after simulated encryption
- Conducting tabletop exercises or live recovery drills for ransomware scenarios
- Auditing disaster recovery readiness as part of compliance or cyber insurance requirements
Do not use for active incident response during a live ransomware attack. Use dedicated IR playbooks instead.
Prerequisites
- Isolated recovery test environment (air-gapped or network-segmented lab)
- Access to backup infrastructure (Veeam, Commvault, Rubrik, AWS Backup, Azure Backup)
- Documented RTO/RPO targets per application tier from business impact analysis
- Backup copies available for restore testing (production replicas or test snapshots)
- Recovery runbooks with step-by-step procedures for each critical system
Workflow
Step 1: Define Recovery Test Scope
Identify critical systems and their tiered recovery targets:
| Tier | System Type | RTO Target | RPO Target | Example |
|---|---|---|---|---|
| Tier 1 | Mission-critical | < 1 hour | < 15 min | Active Directory, core database |
| Tier 2 | Business-critical | < 4 hours | < 1 hour | ERP, email, CRM |
| Tier 3 | Business-operational | < 24 hours | < 4 hours | File shares, internal apps |
| Tier 4 | Non-critical | < 72 hours | < 24 hours | Dev/test, analytics |
Step 2: Prepare Test Environment
# Verify isolated recovery network is segmented
# No routes to production should exist
ip route show | grep -v "192.168.100.0/24" # recovery VLAN only
# Verify backup catalog is accessible
restic snapshots --repo s3:s3.amazonaws.com/backup-bucket --password-file /etc/restic/pw
# Or for Veeam:
# Get-VBRBackup | Where-Object {$_.JobType -eq "Backup"} | Select Name, LastPointCreationTimeStep 3: Execute Restore and Measure RTO
For each tiered system, measure the full recovery timeline:
- Detection to Decision - Time from simulated alert to restore decision
- Backup Locate - Time to identify and select the correct clean restore point
- Restore Execution - Time to restore data/VM/application from backup
- Validation - Time to verify data integrity and application functionality
- Service Restoration - Time until the system is fully operational
Recovery Timeline Measurement:
T0: Incident declared (simulated ransomware detection)
T1: Recovery team assembled and backup identified
T2: Restore initiated from clean backup
T3: Restore completed, integrity checks passed
T4: Application validated and service restored
Actual RTO = T4 - T0
Actual RPO = T0 - backup_timestampStep 4: Validate Data Integrity Post-Restore
# Compare file counts between backup manifest and restored data
find /restored/data -type f | wc -l
# Compare against pre-backup manifest
# Verify database consistency after restore
pg_isready -h localhost -p 5432
psql -c "SELECT count(*) FROM critical_table;" -d restored_db
# Hash verification of critical files
sha256sum /restored/data/critical_config.xml
# Compare against known-good hash from backup manifestStep 5: Test Credential Rotation and Security Hardening
After restore, validate that security controls are re-established:
- Rotate all service account passwords and API keys
- Verify MFA is enabled on all administrative accounts
- Confirm EDR/AV agents are running and reporting to management console
- Validate firewall rules block known C2 indicators
- Check that restored systems have latest security patches
Step 6: Document Results and Calculate Gap
Recovery Test Report:
System: [Name]
Tier: [1-4]
RTO Target: [target] Actual RTO: [measured] Gap: [delta]
RPO Target: [target] Actual RPO: [measured] Gap: [delta]
Data Integrity: [PASS/FAIL]
Application Validation: [PASS/FAIL]
Security Controls Restored: [PASS/FAIL]
Status: [MEETS TARGET / EXCEEDS TARGET / FAILS TARGET]
Remediation Required: [description if FAILS]Show full SKILL.md (257 more words)Show less
Key Concepts
| Term | Definition |
|---|---|
| RTO | Recovery Time Objective: maximum acceptable downtime for a system after a disaster |
| RPO | Recovery Point Objective: maximum acceptable data loss measured in time |
| WRT | Work Recovery Time: time to verify system integrity after restore completes |
| MTD | Maximum Tolerable Downtime: absolute limit before unacceptable business impact |
| Clean Restore Point | A backup verified to be free of ransomware artifacts or encryption |
| Recovery Sequencing | The order in which interdependent systems must be restored |
| Air-Gapped Backup | Backup stored on media physically disconnected from the network |
Tools & Systems
| Tool | Purpose |
|---|---|
| Veeam Backup & Replication | VM and physical server backup and restore |
| Commvault | Enterprise data protection and recovery orchestration |
| Rubrik | Cloud-native backup with ransomware recovery SLA |
| AWS Backup | Centralized backup for AWS services |
| Azure Backup | Microsoft cloud backup with immutable vault |
| Restic | Open-source encrypted backup tool |
| Velero | Kubernetes cluster backup and restore |
Common Pitfalls
- Not testing restores regularly: Backups that are never tested often fail when needed. Test quarterly at minimum.
- Ignoring recovery sequencing: Restoring an application before its database dependency causes cascading failures.
- Skipping credential rotation: Restored systems may contain compromised credentials that allow re-infection.
- Using production network for testing: Recovery tests on production networks risk spreading simulated or real infections.
- Measuring RTO without WRT: Restore completion is not recovery completion. Include validation and hardening time.
- No immutable backups: If ransomware can encrypt or delete backups, recovery is impossible. Use air-gapped or immutable storage.
References
- NIST SP 800-184: Guide for Cybersecurity Event Recovery
- CISA Ransomware Guide: https://www.cisa.gov/stopransomware
- Veeam RTO/RPO Best Practices: https://www.veeam.com/blog/recovery-time-recovery-point-objectives.html
- NIST CSF 2.0 RC.RP (Recovery Planning)
© mukul975, 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
SKILL.md and 3 other files (scripts, references) in skills/testing-ransomware-recovery-procedures of mukul975/Anthropic-Cybersecurity-Skills.
- SKILL.md
- LICENSE
- references/api-reference.md
- scripts/agent.py
Open the folder on GitHubat commit 54a7988
Compare with similar skills
Testing Ransomware Recovery Procedures 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 |
|---|---|---|---|---|---|---|
| Testing Ransomware Recovery Procedures this skillmukul975/Anthropic-Cybersecurity-Skills | 34k | — | ~1.9k | Automated safety check: Pass | Apache-2.0 | |
| Storage S3 Resiliency Expertiseaws/tools-for-devops-agent | 103 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| Frontmcp Production Readinessagentfront/frontmcp | 146 | — | ~6.5k | Automated safety check: Pass | Apache-2.0 | |
| Source Leak Huntuphiago/recon-skills | 1.3k | — | ~2.2k | Automated safety check: Notes | MIT | |
| Pyats Asa Firewallautomateyournetwork/netclaw | 676 | — | ~2.8k | Automated safety check: Pass | Apache-2.0 | |
| OmniRoute Backup and Sync CLIdiegosouzapw/OmniRoute | 75k | — | ~948 | Automated safety check: Pass | MIT |
Similar skills
- Official
Frontmcp Production Readiness
agentfront/frontmcp
Pre-production audit, hardening, and go-live checklists for FrontMCP servers.
Source Leak Hunt
uphiago/recon-skills
Mass scan for exposed env files, backups, and git configs. An agent skill from uphiago/recon-skills.
Pyats Asa Firewall
automateyournetwork/netclaw
Cisco ASA firewall operations via pyATS — VPN sessions, failover state, interfaces, routing, service policies, resource usage, AnyConnect monitoring.
OmniRoute Backup and Sync CLI
diegosouzapw/OmniRoute
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
Pymobiledevice3 Device Operator
doronz88/pymobiledevice3
Operate iOS and iPadOS devices with pymobiledevice3, from a local checkout or straight from PyPI via uvx on a fresh workstation.
More from mukul975/Anthropic-Cybersecurity-Skills
All 644 skills in this repoCampaign Attribution Evidence Analysis
mukul975/Anthropic-Cybersecurity-Skills
Weighs infrastructure, TTP, malware code and timing evidence with the Diamond Model and competing hypotheses to reach a confidence-rated attribution.
Go Malware Analysis in Ghidra
mukul975/Anthropic-Cybersecurity-Skills
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
LNK and Jump List Forensics
mukul975/Anthropic-Cybersecurity-Skills
Guides forensic analysis of Windows LNK shortcut files and Jump Lists with LECmd, JLECmd and manual parsing to show file access and program execution.
Malware Persistence Analysis with Autoruns
mukul975/Anthropic-Cybersecurity-Skills
Hunts Windows malware persistence with Sysinternals Autoruns, covering run keys, services, scheduled tasks and drivers, with baseline comparison.
NTFS MFT Deleted File Recovery
mukul975/Anthropic-Cybersecurity-Skills
Guides a Windows forensic examination of the NTFS Master File Table to recover deleted-file evidence, build timelines and spot timestomping.
Network Covert Channel Analysis
mukul975/Anthropic-Cybersecurity-Skills
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Related
Categories
Questions about Testing Ransomware Recovery Procedures
What does Testing Ransomware Recovery Procedures do?
Tests and validates ransomware recovery procedures - backup restore operations (e.g. Testing Ransomware Recovery Procedures is an agent skill from mukul975/Anthropic-Cybersecurity-Skills.g.
When should I use Testing Ransomware Recovery Procedures?
Testing Ransomware Recovery Procedures fits situations like: validating that recovery plans work under realistic conditions; measuring RTO/RPO against business requirements; testing restore integrity after simulated encryption.
How do I install Testing Ransomware Recovery Procedures in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a claude-code`. Or copy the skill folder (skills/testing-ransomware-recovery-procedures in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/testing-ransomware-recovery-procedures in your project. Claude Code loads it when a task matches its description.
How do I install Testing Ransomware Recovery Procedures in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a codex`. Or copy the skill folder (skills/testing-ransomware-recovery-procedures in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/testing-ransomware-recovery-procedures in your project. Codex loads it when a task matches its description.
Can I use Testing Ransomware Recovery Procedures 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 mukul975/Anthropic-Cybersecurity-Skills --skill testing-ransomware-recovery-procedures -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/testing-ransomware-recovery-procedures, .gemini/skills/testing-ransomware-recovery-procedures, .github/skills/testing-ransomware-recovery-procedures and .opencode/skills/testing-ransomware-recovery-procedures in your project.
What does Testing Ransomware Recovery Procedures need to run?
Going by SKILL.md and its folder, Testing Ransomware Recovery Procedures needs Python for the scripts in its folder and the command-line tools its instructions call (psql). Our summary lists: Python 3.
Does Testing Ransomware Recovery Procedures access the network?
SKILL.md names 2 domains. As links in the text: cisa.gov and veeam.com. This is read from the text; nothing was executed.
Is Testing Ransomware Recovery Procedures 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Testing Ransomware Recovery Procedures use?
Testing Ransomware Recovery Procedures is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Testing Ransomware Recovery Procedures use?
About 1.9k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 975 tokens, read only when the agent opens those files.
What are the alternatives to Testing Ransomware Recovery Procedures?
Skills that share tags, products or a category with Testing Ransomware Recovery Procedures: Storage S3 Resiliency Expertise (aws/tools-for-devops-agent, 103 stars), Frontmcp Production Readiness (agentfront/frontmcp, 146 stars), Source Leak Hunt (uphiago/recon-skills, 1.3k stars) and Pyats Asa Firewall (automateyournetwork/netclaw, 676 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Testing Ransomware Recovery Procedures?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.
Source: mukul975/Anthropic-Cybersecurity-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.