Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add selvarajmurugesan90/ops-engineering-skills --skill disaster-recovery-and-backup-strategygit clone --depth 1 https://github.com/selvarajmurugesan90/ops-engineering-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/disaster-recovery-and-backup-strategy)<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/disaster-recovery-and-backup-strategy"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/disaster-recovery-and-backup-strategy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/selvarajmurugesan90/ops-engineering-skills/disaster-recovery-and-backup-strategy"><img src="https://agentmods.dev/badge/skills/selvarajmurugesan90/ops-engineering-skills/disaster-recovery-and-backup-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00127 | $0.03297 |
| Opus 5.5 | $0.00051 | $0.01319 |
| Sonnet 5.5 | $0.00025 | $0.00659 |
| Haiku 4.5 | $0.00013 | $0.00330 |
Grade A, and why
disaster-recovery-and-backup-strategy scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disaster Recovery and Backup Strategy
Purpose
Backups that have never been restored, and DR plans that have never been tested with a real failover, are aspirational documents, not operational capabilities — the outage or ransomware event is the worst possible time to discover a backup is corrupt, a runbook step references a decommissioned system, or the cross-region replica has silent lag. This skill covers picking a DR pattern (backup-restore through active-active) matched to a genuine Recovery Time Objective (RTO) and Recovery Point Objective (RPO) rather than the most expensive option by default, implementing cross-region/cross-account backup replication that survives the loss of the primary account itself, and — critically — testing failover on a schedule so the plan is proven, not assumed.
When to use
- Defining or revisiting RTO/RPO targets for a workload or the organization's tiered criticality model.
- Designing backup strategy for a database, storage account/bucket, or entire application stack, including cross-region and cross-account/ subscription/project replication.
- Choosing a DR pattern: backup-restore, pilot light, warm standby, or multi-site active-active.
- Planning and running a DR failover test (tabletop or live).
- Responding to a real regional outage, ransomware/mass-deletion event, or a compliance requirement mandating documented, tested DR.
- Auditing existing backups for actual restorability (as opposed to "a backup job completed successfully").
Prerequisites & environment
- A criticality tiering for workloads (e.g. Tier 0 = customer-facing revenue path, Tier 1 = internal but business-critical, Tier 2 = everything else) with an agreed RTO/RPO per tier, signed off by the business — not decided unilaterally by engineering, since DR pattern cost scales steeply as RTO/RPO approach zero.
- Native backup tooling access: AWS Backup (centralized, supports EBS, RDS, DynamoDB, EFS, S3), Azure Backup / Azure Site Recovery, or GCP Backup and DR Service, plus each data service's own point-in-time-recovery/snapshot feature (RDS automated backups, Azure SQL PITR, Cloud SQL automated backups).
- Cross-region (and ideally cross-account/subscription/project) write access for backup replication targets, following the isolation boundaries established in the landing-zone skills — a backup that lives only in the same account as the primary data does not protect against account-level compromise or accidental account deletion.
- A tested, version-controlled DR runbook (Infrastructure as Code for the DR-site infrastructure itself, plus documented manual steps for anything not yet automated) — a plan that exists only as institutional knowledge in one engineer's head is not a DR plan.
- Executive/business sign-off on the DR pattern's cost, since warm standby and active-active both roughly double (or more) infrastructure spend compared to backup-restore.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 288 lines · 127 tokens per session scan A ea4aa17ea330
disaster-recovery-and-backup-strategy is a skill published in the GitHub repository selvarajmurugesan90/ops-engineering-skills (42 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 127 tokens to every session and 3,297 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".