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 dungnotnull/hybrid-harness-chaos-process-prm --skill s29-disaster-recoverygit clone --depth 1 https://github.com/dungnotnull/hybrid-harness-chaos-process-prmWrote 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/dungnotnull/hybrid-harness-chaos-process-prm/s29-disaster-recovery)<a href="https://agentmods.dev/skills/dungnotnull/hybrid-harness-chaos-process-prm/s29-disaster-recovery"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s29-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/dungnotnull/hybrid-harness-chaos-process-prm/s29-disaster-recovery"><img src="https://agentmods.dev/badge/skills/dungnotnull/hybrid-harness-chaos-process-prm/s29-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.00118 | $0.03926 |
| Opus 5 | $0.00059 | $0.01963 |
| Sonnet 5 | $0.00024 | $0.00785 |
| Haiku 4.5 | $0.00012 | $0.00393 |
Grade A, and why
disaster-recovery-business-continuity 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 12d 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 — 464 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Disaster Recovery & Business Continuity (s29)
Purpose
Move beyond component-level chaos into organization-level disaster resilience — defining RTO/RPO targets, implementing backup and restore procedures, orchestrating multi-region failover, and validating that the business can survive the worst-case scenario.
Prerequisites
- Service topology and architecture diagrams
- Resilience scores from s26
- Compliance audit trail from s30 (if available)
- Cloud provider access for failover operations
- Velero or equivalent backup solution configured
Input Contract
| Input | Source | Required |
|---|---|---|
| Infrastructure topology (regions, AZs, providers) | s01, s05 | Yes |
| Critical service inventory with dependencies | s01 (PRD component inventory) | Yes |
| Resilience scores (all services) | s26 output | Yes |
| Chaos experiment results (identifies single points of failure) | s14-s21 outputs | Yes |
| Backup infrastructure details | s05 (infra definitions) | Yes |
| RTO/RPO targets (business requirements) | s01 (PRD — NFR constraints) | Yes |
| Compliance requirements | s30 (audit/compliance) | No |
Output Contract
| Output | Destination | Format |
|---|---|---|
| DR plan document | .commandcode/artifacts/dr/dr-plan.md |
Markdown |
| RTO/RPO matrix per service | .commandcode/artifacts/dr/rto-rpo-matrix.yaml |
YAML |
| Failover runbook | .commandcode/artifacts/dr/failover-runbook.md |
Markdown |
| Backup configuration | .commandcode/artifacts/dr/backup-config.yaml |
YAML |
| DR test schedule | .commandcode/artifacts/dr/dr-test-schedule.yaml |
YAML |
| DR test results | s26 (resilience score contribution) | JSON |
| Recovery scripts | .commandcode/artifacts/dr/scripts/ |
Bash/Python |
| Business impact analysis | s30 (compliance evidence) | Markdown |
DR Planning Framework
ASSESS → DESIGN → IMPLEMENT → TEST → MAINTAIN
Assess: Business impact analysis, RTO/RPO targets, critical path mapping
Design: Multi-region architecture, backup strategy, failover mechanism
Implement: Backup schedules, replication, DNS failover, infrastructure automation
Test: DR drills, tabletop exercises, full region failover
Maintain: Quarterly review, update for new services, validate backups
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.
- 12d ago First seen · 464 lines · 118 tokens per session scan A b54108569495
disaster-recovery-business-continuity is a skill published in the GitHub repository dungnotnull/hybrid-harness-chaos-process-prm (19 stars, last pushed 3mo ago), licensed MIT. It adds 118 tokens to every session and 3,926 once invoked, about $0.0006 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…