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 kensaurus/cursor-kenji --skill plan-backup-drgit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/plan-backup-dr)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/plan-backup-dr"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/plan-backup-dr/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/kensaurus/cursor-kenji/plan-backup-dr"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/plan-backup-dr.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.00074 | $0.01374 |
| Opus 5.5 | $0.00030 | $0.00550 |
| Sonnet 5.5 | $0.00015 | $0.00275 |
| Haiku 4.5 | $0.00007 | $0.00137 |
Grade A, and why
plan-backup-dr 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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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)
- Propose — backup, restore path, drill, or off-provider export
- Risk — worst-case in plain language ("lose up to a day of uploads")
- Keep-working — stores that already have a proven restore
- Phase — P0 / P1 / P2 (do not execute)
Worked example
Propose: run one isolated restore drill of the primary DB; write the runbook from what you actually did. Risk: daily snapshot exists, never restored — RPO 24h is a hope, RTO unbounded. Keep-working: object-storage versioning already on. Phase: P0 — no proven restore. Target: drill into an isolated env, never over prod.
Phase 0 — Map the recovery surface [HIGH freedom]
For each stateful thing, find backup and restore:
- Primary DB (Supabase/Postgres): PITR? snapshots? retention? who restores?
- Object storage: versioning? lifecycle that deletes? backed up at all?
- Secrets & config: reconstructable if the account vanished?
- Auth users: identities recoverable, or only app rows?
- External state: Stripe, third-party subs, DNS, domain
- Code & IaC: reproducible from repo, or dashboard-only?
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.
- 1mo ago First seen · 132 lines · 74 tokens per session scan A 379960f7d36e
plan-backup-dr is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 74 tokens to every session and 1,374 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
caching-cdn-strategy-planner
Designs multi-layer caching strategy with edge CDN, server-side caching, cache invalidation, and CDN configuration. Use for "caching strategy", "CDN setup", "cache invalidation", or "performance optimization".
qdrant-managed-cloud-quickstart
Getting a first Qdrant Managed Cloud cluster running and connected safely: Free, Standard, and Premium tiers, choices that can't be changed later, creating clusters from the Console or the qcloud CLI, Database API keys, ports and TLS, strict mode on new collections, Cloud Inference, and what to set before relying on a…
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.
create-migration
Create a new database migration following project naming and safety rules. Use when the user asks to add a migration or create a migration for a schema change.
aws-cost-estimator
Estimate or review cost for proposed AWS resources (compute, storage, data transfer). Use when the user asks for cost estimate or cost optimization.
opensearch
Workflow for OpenSearch (or Elasticsearch) usage: indexing, search, mappings, and tuning. Use when the user asks about OpenSearch/Elasticsearch.