db-backup-restore

db-backup-restore is a skill for Claude Code, Codex from m-binimran/dev-pack. It costs 58 tokens per session (400 once invoked), scanned A, original, MIT.

A runbook for backing up and restoring PostgreSQL or Supabase databases, including logical dumps, managed backups, point-in-time recovery, and verification.

In plain words
What is it for?
Use it before migrations, for disaster recovery, or when copying production data to staging, with guidance for safe restores, checks, storage, and approvals.
Why use it?
It provides a repeatable way to protect data before risky changes and to test that backups can actually restore a working database without silently losing records.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it before migrations, for disaster recovery, or when copying production data to staging, with guidance for safe restores, checks, storage, and approvals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/m-binimran/dev-pack/db-backup-restore
Install

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.

Any agent
npx skills add m-binimran/dev-pack --skill db-backup-restore
Clone the repo
git clone --depth 1 https://github.com/m-binimran/dev-pack

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for db-backup-restore

README.md
[![agentmods](https://agentmods.dev/badge/skills/m-binimran/dev-pack/db-backup-restore/github.svg)](https://agentmods.dev/skills/m-binimran/dev-pack/db-backup-restore)
Your own site
<a href="https://agentmods.dev/skills/m-binimran/dev-pack/db-backup-restore"><img src="https://agentmods.dev/badge/skills/m-binimran/dev-pack/db-backup-restore/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.

agentmods 80×15 button for db-backup-restore

Your own site · 80×15
<a href="https://agentmods.dev/skills/m-binimran/dev-pack/db-backup-restore"><img src="https://agentmods.dev/badge/skills/m-binimran/dev-pack/db-backup-restore.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 400 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.00400
Opus 5.5 $0.00023 $0.00160
Sonnet 5.5 $0.00012 $0.00080
Haiku 4.5 $0.00006 $0.00040

Measured 2mo ago against content hash 4837f868f109, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

db-backup-restore 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 2mo 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.

skills/db-backup-restore/SKILL.md · 32 lines

What it actually says

db-backup-restore

Backups are only real if you've restored one. Treat restore as the thing you're actually buying.

Back up

  • Logical (portable): pg_dump --format=custom --no-owner --file=backup.dump "$DATABASE_URL". Custom format restores selectively and in parallel.
  • Supabase: managed daily backups; enable Point-in-Time Recovery (PITR) for anything important.
  • Before a risky migration: take a fresh dump first. Note the timestamp and what it covers.
  • Store backups off the database host. Never commit a dump (it's data — and may contain PII).

Restore (runbook)

  1. Restore into a NEW/empty target first (staging or a scratch DB), never straight over a live one: pg_restore --no-owner --clean --if-exists -d "$TARGET_URL" backup.dump
  2. Verify row counts and a few key records match expectations before pointing anything at it.
  3. Only then, if replacing prod, do it in a maintenance window with a fresh backup taken immediately prior.

Safety

  • Never restore over production without an explicit human OK and a just-taken backup. A restore is destructive — it can overwrite newer data.
  • Test the restore path periodically; an untested backup is a hope, not a recovery plan.
  • Scrub or limit PII when cloning prod → staging.

Output

  • The exact backup/restore commands for the situation, the target (never prod by default), and the verification step. State clearly when an action is destructive.
Changes

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.

  1. 2mo ago First seen · 32 lines · 58 tokens per session scan A 4837f868f109

Subscribe to this mod's changes

db-backup-restore is a skill published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 4mo ago), licensed MIT. It adds 58 tokens to every session and 400 once invoked, about $0.0002 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-08-31.

Related

Other skills, from other repositories

alloydb-basics

Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.

google/skills · 72 tokens

postgresql-table-design

Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.

wshobson/agents · 37 tokens

db-repair

Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …

garrytan/gbrain · 96 tokens

volcengine-rds-postgresql

A tool for operating PostgreSQL databases hosted by Volcano Engine's managed database service. PostgreSQL is a relational database used to store structured application data.

bytedance/agentkit-samples · 63 tokens

dsql

Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…

awslabs/agent-plugins · 246 tokens

analyzing-insights-across-teams

Analyze PostHog insights, dashboards, or teams beyond the current project by querying the prod Postgres replicas synced into the dogfood data warehouse (US project 2, "PostHog App + Website"). Use when asked to analyze insights across all teams or projects, another team's insights, or fleet-wide insight/dashboard…

PostHog/posthog-foss · 115 tokens