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 ancoleman/ai-design-components --skill planning-disaster-recoverygit clone --depth 1 https://github.com/ancoleman/ai-design-componentsWrote 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/ancoleman/ai-design-components/planning-disaster-recovery)<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/planning-disaster-recovery"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/planning-disaster-recovery/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/ancoleman/ai-design-components/planning-disaster-recovery"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/planning-disaster-recovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00058 | $0.02913 |
| Opus 5.5 | $0.00023 | $0.01165 |
| Sonnet 5.5 | $0.00012 | $0.00583 |
| Haiku 4.5 | $0.00006 | $0.00291 |
Grade A, and why
planning-disaster-recovery 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 2mo 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disaster Recovery
Purpose
Provide comprehensive guidance for designing disaster recovery (DR) strategies, implementing backup systems, and validating recovery procedures across databases, Kubernetes clusters, and cloud infrastructure. Enable teams to define RTO/RPO objectives, select appropriate backup tools, configure automated failover, and test DR capabilities through chaos engineering.
When to Use This Skill
Invoke this skill when:
- Defining recovery time objectives (RTO) and recovery point objectives (RPO)
- Implementing database backups with point-in-time recovery (PITR)
- Setting up Kubernetes cluster backup and restore workflows
- Configuring cross-region replication for high availability
- Testing disaster recovery procedures through chaos experiments
- Meeting compliance requirements (GDPR, SOC 2, HIPAA)
- Automating backup monitoring and alerting
- Designing multi-cloud disaster recovery architectures
Core Concepts
RTO and RPO Fundamentals
Recovery Time Objective (RTO): Maximum acceptable downtime after a disaster before business impact becomes unacceptable.
Recovery Point Objective (RPO): Maximum acceptable data loss measured in time. Defines how far back in time recovery must reach.
Criticality Tiers:
- Tier 0 (Mission-Critical): RTO < 1 hour, RPO < 5 minutes
- Tier 1 (Production): RTO 1-4 hours, RPO 15-60 minutes
- Tier 2 (Important): RTO 4-24 hours, RPO 1-6 hours
- Tier 3 (Standard): RTO > 24 hours, RPO > 6 hours
3-2-1 Backup Rule
Maintain 3 copies of data on 2 different media types with 1 copy offsite.
Example implementation:
- Primary: Production database
- Secondary: Local backup storage
- Tertiary: Cloud backup (S3/GCS/Azure)
Backup Types
Full Backup: Complete copy of all data. Slowest to create, fastest to restore.
Incremental Backup: Only changes since last backup. Fastest to create, requires full + all incrementals to restore.
Differential Backup: Changes since last full backup. Balance between storage and restore speed.
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/chaos/db-failover-test.sh 23 KB runs code
- examples/chaos/region-failure-test.sh 19 KB runs code
- examples/postgresql/pgbackrest-config/README.md 1.3 KB
- examples/runbooks/database-failover.md 15 KB
- examples/runbooks/region-failover.md 24 KB
- outputs.yaml 17 KB
- references/chaos-engineering.md 2.5 KB
- references/cloud-dr-patterns.md 4.2 KB
- references/compliance-retention.md 3.1 KB
- references/cross-region-replication.md 2.1 KB
- references/database-backups.md 1.9 KB
- references/kubernetes-dr.md 3.1 KB
- references/rto-rpo-planning.md 10.0 KB
- references/runbook-automation.md 4.2 KB
- scripts/check-retention.sh 391 B runs code
- scripts/dr-drill.sh 396 B runs code
- scripts/generate-dr-report.sh 399 B runs code
- scripts/test-restore.sh 241 B runs code
- scripts/validate-backup.sh 813 B runs code
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.
- 2mo ago First seen · 329 lines · 58 tokens per session scan A e335a0a71e74
planning-disaster-recovery is a skill published in the GitHub repository ancoleman/ai-design-components (527 stars, last pushed 11mo ago), licensed MIT. It adds 58 tokens to every session and 2,913 once invoked, about $0.0002 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.
planning-disaster-recovery compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| planning-disaster-recoveryancoleman/ai-design-components | Skill | 527 | 11mo ago | MIT | A | 58 | Claude Code |
| cb-analytics-capellacelticht32/Couchbase-Skills-for-Claude.ai | Skill | 4 | 4mo ago | MIT | A | 89 | Claude Code, Codex |
| couchbase-capellacelticht32/Couchbase-Skills-for-Claude.ai | Skill | 4 | 4mo ago | MIT | A | 180 | Claude Code, Codex |
| ai-persistence/build-cloudflare-artifact-storeTanStack/ai | Skill | 3.3k | yesterday | MIT | A | 104 | Claude Code |
| ai-persistence/build-cloudflare-adapterTanStack/ai | Skill | 3.3k | yesterday | MIT | A | 68 | Claude Code |
| rdsitsmostafa/aws-agent-skills | Skill | 1.2k | 4d ago | MIT | A | 31 | Claude Code |
| cost-optimizationrampstackco/claude-skills | Skill | 1.0k | 11d ago | MIT | A | 101 | Claude Code |