plan-backup-dr SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
plan-backup-dr from kensaurus/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kensaurus/skills/plan-backup-dr@git:20260923.68c095ePins git:20260923.68c095e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kensaurus/skills
- Path
skills/plan-backup-dr/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260923.68c095e, committed Sep 23, 2026
- First version recorded
- Aug 18, 2026
- Size
- 5,507 bytes
- Repository stars
- 9
- License
- MIT
Plan-only audit of whether a project can actually recover from data loss, not just whether backups exist. Use when "can we recover if the DB dies", "audit our backups", "what's our RPO/RTO", or "disaster recovery".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# plan-backup-dr — Recovery capability plan **Degree of freedom: HIGH** — prove restore, quantify RPO/RTO, plan. Stay **plan-only**. No PITR toggles or prod-writing drills until approved. **Role:** Platform / disaster-recovery engineer. **Task:** Prove restore works, quantify RPO/RTO, emit `plan-backup-dr.md`. **Audit & plan only — no PITR toggles, lifecycle edits, or drills that write to prod until approved.** **Backup existence is not recovery capability.** An untested backup is a hope. ## This skill vs neighbors | Skill | Owns | |---|---| | **plan-backup-dr** (this) | Can you restore? RPO/RTO, drill evidence, SPOF | | `plan-data-integrity` | Stop destructive ops *going forward* (unguarded DELETE/DROP) | | `audit-env-parity` | Staging pointing at prod data (blast-radius setup) | | `audit-infra-cost` | Backup retention that silently explodes the bill | | `plan-secrets-audit` | Credential exposure — not "can I reconstruct secrets after loss" | Do **not** fire for "is this migration safe / agent might delete prod" → `plan-data-integrity`. That skill *prevents* wipe; this one *recovers* after one. ## How to reason (every plan item) …
Read the whole file at its exact version.
How to install
mdr add kensaurus/skills/plan-backup-dr@sha256:572722bb39ca90b2The line at the top of this page pins the label git:20260923.68c095e, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qe444w32uq3i67eo)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 18, 2026 and Sep 23, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260923.68c095e latest | 2026-09-23 | 68c095e | 5,507 B | A | view · diff |
| git:20260923.cf348bd | 2026-09-23 | cf348bd | 5,591 B | A | view · diff |
| git:20260819.170df67 | 2026-08-19 | 170df67 | 5,375 B | A | view · diff |
| git:20260818.274c4d7 | 2026-08-18 | 274c4d7 | 4,098 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (5507 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
kensaurus/skills · 9 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qe444w32uq3i67eo GET https://markdownregistry.com/api/v1/resolve?ref=kensaurus/skills/plan-backup-dr GET https://markdownregistry.com/api/v1/blob/572722bb39ca90b263290afad19f7aef11433057f6d6a32823d491288e298222
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kensaurus/skills
Every file in kensaurus/skills