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.
git clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/commands/thelobbi/claude/disaster-recovery)<a href="https://agentmods.dev/commands/thelobbi/claude/disaster-recovery"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/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/commands/thelobbi/claude/disaster-recovery"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/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.00000 | $0.03894 |
| Opus 5 | $0.00000 | $0.01947 |
| Sonnet 5 | $0.00000 | $0.00779 |
| Haiku 4.5 | $0.00000 | $0.00389 |
Grade A, and why
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 9d 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 — 455 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disaster Recovery Planning & Testing
Comprehensive disaster recovery planning, testing, and validation with RTO/RPO requirements, failover procedures, data backup strategies, and business continuity planning.
Purpose
Design, implement, test, and validate comprehensive disaster recovery and business continuity plans to ensure business resilience against catastrophic failures, including data center outages, regional disasters, cyberattacks, and data corruption.
Multi-Agent Coordination Strategy
Uses scenario-based DR testing pattern where disaster scenarios are simulated, recovery procedures executed, and business continuity validated across people, process, and technology dimensions.
DR Planning Architecture
``` ┌──────────────────────────────────────────────────┐ │ DR Command Center │ │ (dr-orchestrator) │ └────────────┬─────────────────────────────────────┘ │ ┌────────┼────────┬────────┬────────┬─────────┐ ▼ ▼ ▼ ▼ ▼ ▼ Assess Design Implement Test Validate Document ```
Execution Flow
Phase 1: Business Impact Analysis (0-30 mins)
- bia-analyst - Business Impact Analysis
- critical-service-identifier - Identify critical business services
- rto-rpo-calculator - Calculate RTO/RPO requirements
- dependency-mapper - Map service dependencies
- impact-assessor - Assess financial/reputation impact
- compliance-validator - Identify regulatory DR requirements
Phase 2: Risk Assessment (30-60 mins)
- disaster-scenario-modeler - Model disaster scenarios
- threat-analyzer - Analyze disaster threats (natural, technical, human)
- vulnerability-assessor - Assess DR vulnerabilities
- probability-calculator - Calculate disaster probabilities
- risk-scorer - Score and prioritize risks
Phase 3: DR Strategy Design (60-120 mins)
- dr-strategy-architect - Design overall DR strategy
- backup-strategist - Design backup strategy (3-2-1 rule)
- replication-designer - Design data replication approach
- failover-architect - Design failover mechanisms
- multi-region-planner - Multi-region DR architecture
- rto-optimizer - Optimize for RTO targets
- rpo-optimizer - Optimize for RPO targets
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.
- 9d ago First seen · 455 lines · 0 tokens per session scan A c0be28c2d0c0
disaster-recovery is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,894 tokens. 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-31.
Other commands, from other repositories
cost-optimize
You are a cloud cost optimization expert specializing in reducing infrastructure expenses while maintaining performance and reliability. Analyze cloud spending, identify savings opportunities, and implement cost-effective architectures across AWS, Azure, GCP, and OCI. Where provider-specific code appears below, adapt…
deploy
Deploy a frontend (React, Next.js, or static HTML) to a live URL on Butterbase.
integrate
Set up third-party service integrations.
env
Manage Vercel environment variables. Commands include list, pull, add, remove, and diff. Use to sync environment variables between Vercel and your local development environment.
scan
Scan AWS account for cost optimization.
finops-feedback
Step 5 (Feedback Loop & Celebration) — measure realized against projected savings, compute a labelled Cloud Entropy proxy, close the opportunity, and emit at least one new idea or policy update so the loop actually closes. Applies the double-loop gate. Mutates on the closure path.