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/Mr-chen-05/rules-2.1-optimizedWrote 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/rules/mr-chen-05/rules-2.1-optimized/disaster-recovery-plan)<a href="https://agentmods.dev/rules/mr-chen-05/rules-2.1-optimized/disaster-recovery-plan"><img src="https://agentmods.dev/badge/rules/mr-chen-05/rules-2.1-optimized/disaster-recovery-plan/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/rules/mr-chen-05/rules-2.1-optimized/disaster-recovery-plan"><img src="https://agentmods.dev/badge/rules/mr-chen-05/rules-2.1-optimized/disaster-recovery-plan.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.04507 | $0.04507 |
| Opus 5 | $0.02253 | $0.02253 |
| Sonnet 5 | $0.00901 | $0.00901 |
| Haiku 4.5 | $0.00451 | $0.00451 |
Grade A, and why
disaster-recovery-plan 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 — 700 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨 灾难恢复计划
韧性保障: 面对意外情况，确保系统能够快速恢复，最大限度减少数据丢失和服务中断。
一、灾难场景分类
1.1 数据丢失类
项目记忆文件损坏: 严重程度: 🔴 高 影响范围: - project.context.md 完全损坏 - 部分内容不可读 - 关键区块缺失 - 元数据错误
恢复优先级: P0 恢复目标时间 (RTO): <5分钟 恢复点目标 (RPO): <15分钟
配置文件误删: 严重程度: 🟠 中 影响范围: - .rules/ 目录被删除 - MCP配置丢失 - 模板文件缺失 - 脚本文件丢失
恢复优先级: P1 恢复目标时间: <10分钟 恢复点目标: <1小时
重要决策记录丢失: 严重程度: 🟡 中-低 影响范围: - Decisions区块为空 - TODO项目丢失 - Notes内容缺失
恢复优先级: P2 恢复目标时间: <30分钟 恢复点目标: <4小时
用户数据意外清除: 严重程度: 🔴 高 影响范围: - 代码文件被删 - 项目文件丢失 - 敏感信息泄露
恢复优先级: P0 恢复目标时间: 立即 恢复点目标: <5分钟
1.2 系统故障类
超级大脑系统崩溃: 严重程度: 🔴 高 症状表现: - 激活流程失败 - Context记录无响应 - Memory系统错误 - 推荐引擎失效
恢复策略: 1. 检测崩溃原因 2. 重置系统状态 3. 重新激活 4. 验证功能
MCP工具全部失效: 严重程度: 🔴 高 症状表现: - 文件操作失败 - GitHub连接中断 - Memory无法访问 - 所有工具超时
恢复策略: 1. 检查MCP配置 2. 重启MCP服务 3. 降级到基础模式 4. 手动操作辅助
规则加载失败: 严重程度: 🟠 中 症状表现: - .rules目录不可读 - 规则文件损坏 - 优先级冲突 - 语法错误
恢复策略: 1. 验证规则文件 2. 修复语法错误 3. 解决冲突 4. 重新加载
死循环或无限递归: 严重程度: 🟠 中 症状表现: - 系统hang住 - CPU 100% - 内存持续增长 - 无响应
恢复策略: 1. 强制中断 2. 识别循环点 3. 修复逻辑 4. 添加保护
1.3 安全事件类
敏感信息泄露: 严重程度: 🔴 高 事件类型: - 密码/Token泄露 - API密钥暴露 - 个人信息公开 - 内部数据外泄
响应流程: 1. 立即停止操作 - 撤销已泄露内容 - 轮换密钥/Token - 通知相关方 - 安全审计
未授权操作执行: 严重程度: 🟠 中-高 事件类型: - 权限绕过 - 强制执行 - 恶意命令 - 数据篡改
响应流程: 1. 撤销操作 2. 恢复数据 3. 封锁漏洞 4. 审计日志 5. 权限加固
恶意规则注入: 严重程度: 🟠 中 事件类型: - 规则文件被篡改 - 恶意代码注入 - 后门植入
响应流程: 1. 隔离受影响规则 2. 从备份恢复 3. 扫描所有规则 4. 验证完整性 5. 加强防护
权限绕过: 严重程度: 🔴 高 事件类型: - Level 0规则被绕过 - 安全边界突破 - 强制执行危险操作
响应流程: 1. 立即终止会话 2. 记录详细日志 3. 修复漏洞 4. 加强验证 5. 安全审计
二、预防措施
2.1 自动备份机制
备份策略: 实时备份: - 触发时机: 每次修改前 - 备份对象: 被修改的文件 - 保留策略: 最近3个版本 - 存储位置: .backup/realtime/
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 · 700 lines · 4,507 tokens per session scan A 0809fd168dfd
disaster-recovery-plan is a cursor rule published in the GitHub repository Mr-chen-05/rules-2.1-optimized (173 stars, last pushed 10mo ago), licensed MIT. It adds 4,507 tokens to every session, about $0.0225 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.