backup-and-recovery skillA
backup-and-recovery is agent-read markdown (skill) from cbrock84/headcount: Protects and restores data — backup coverage and scope, retention, immutability against ransomware, and proving restores actually work. Use this to design a backup regime, verify restores, plan retention, protect backups from ransomware, or recover from data loss..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Backup and recovery Nobody wants backups; they want restores. The distinction is not pedantic — organizations discover the difference during the only event that matters. Recovery objectives and which processes must survive are set by `operations:business-continuity-and-resilience`. This skill delivers against them. ## Coverage is where it fails first Most backup gaps are things nobody thought to include: a database somebody stood up outside the standard process, configuration that only exists in a running system, data in a SaaS platform assumed to be the vendor's responsibility, or a developer's machine holding the only copy of something. Reconcile backup coverage against the asset register from `it-operations:it-asset-management` on a cadence and treat the difference as a finding. An untested assumption of coverage is the normal state of affairs. Note that SaaS providers protect against **their** failures, not against your deletion or a malicious insider. Read what the contract actually commits to, rather than what the marketing implies. ## The 3-2-1 shape, and why the offline copy matters …
Read the whole file at its exact version.
How to install
mdr add cbrock84/headcount/backup-and-recovery@git:20260916.e72e404mdr add cbrock84/headcount/backup-and-recovery@sha256:ee09976d32839f02Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_45yypu7pfteeumhz)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.e72e404 latest | 2026-09-16 | e72e404 | 3,952 B | A | view · diff |
| git:20260901.0757404 | 2026-09-01 | 0757404 | 3,613 B | A | view · diff |
| git:20260829.3b7c308 | 2026-08-29 | 3b7c308 | 3,249 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 (3952 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
cbrock84/headcount · 1,664 stars · license MIT · pushed 2026-09-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_45yypu7pfteeumhz GET https://markdownregistry.com/api/v1/resolve?ref=cbrock84/headcount/backup-and-recovery GET https://markdownregistry.com/api/v1/blob/ee09976d32839f024554cc9cc477ae51f87adcb888011a45daa0f2f529124759
Your agent 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.