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/navraj007in/architecture-cowork-pluginWrote 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/navraj007in/architecture-cowork-plugin/disaster-recovery)<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/disaster-recovery"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/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/navraj007in/architecture-cowork-plugin/disaster-recovery"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/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.00018 | $0.01277 |
| Opus 5 | $0.00009 | $0.00639 |
| Sonnet 5 | $0.00004 | $0.00255 |
| Haiku 4.5 | $0.00002 | $0.00128 |
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 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/architect:disaster-recovery
Trigger
/architect:disaster-recovery [options]
Options:
[non_interactive:true]— derive targets from SDL, generate standard runbooks
Purpose
Every system will fail. This command generates a disaster recovery (DR) strategy document with RTO (Recovery Time Objective) and RPO (Recovery Point Objective) targets tailored to your stage, backup configuration, cross-region failover patterns, and incident runbooks. Ensures business continuity and reduces mean-time-to-recovery (MTTR) under pressure.
Workflow
Quick Navigation
| Phase | Steps |
|---|---|
| Setup | Step 1 |
| Generation | Step 2 · Step 3 |
| Completion | Step 4 · Step 5 |
Step 1: Read Context
ℹ️ CONTEXT LOADING: _state.json → SDL → tech stack
Read:
_state.json.project.stage(MVP/growth/enterprise → RTO/RPO targets)_state.json.tech_stack(database, deployment platform)- SDL
nonFunctionalsection for availability targets - Scaffolded infrastructure (docker-compose.yml, k8s configs)
Step 2: Generate RTO/RPO Strategy
Create docs/disaster-recovery/strategy.md:
By stage:
| Stage | Availability SLO | RTO Target | RPO Target | Backup Freq | Multi-Region |
|---|---|---|---|---|---|
| MVP | 99% | 4 hours | 24 hours | Weekly | No |
| Growth | 99.5% | 1 hour | 1 hour | Daily | Maybe (one standby) |
| Enterprise | 99.9% | 15 min | 15 min | Hourly | Yes (active-active) |
Backup configuration:
- Database: daily snapshots (AWS RDS, automated)
- Application state: stored in database (no separate state)
- Secrets: encrypted in AWS Secrets Manager
- Infrastructure-as-code: git repository (single source of truth)
Failover patterns:
- Single-region: RDS automated failover to replica
- Multi-region: DNS failover (Route 53 health checks)
- Active-active: load balancing across regions
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 · 166 lines · 18 tokens per session scan A e6abd43ad259
disaster-recovery is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 18 tokens to every session and 1,277 once invoked, about $0.0001 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-31.
Other commands, from other repositories
nyann:apply
Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…
spec-release
Generate release notes, changelog, and deployment checklist.
aws-research
Research AWS services and architecture patterns using AWS Knowledge MCP for authoritative guidance.
azure-research
Research Azure services and architecture patterns using Microsoft Learn MCP for authoritative guidance.
gcp-research
Research Google Cloud services and architecture patterns using Google Developer Knowledge MCP for authoritative guidance.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.