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 agentmods add skills/m-binimran/dev-pack/db-backup-restorenpx skills add m-binimran/dev-pack --skill db-backup-restoregit clone --depth 1 https://github.com/m-binimran/dev-packWrote 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/m-binimran/dev-pack/db-backup-restore)<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="Measured on agentmods" 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 | $0.00058 | $0.00400 |
| Opus 5 | $0.00029 | $0.00200 |
| Sonnet 5 | $0.00012 | $0.00080 |
| Haiku 4.5 | $0.00006 | $0.00040 |
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 3d 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.
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)
- 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 - Verify row counts and a few key records match expectations before pointing anything at it.
- 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.
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.
- 3d ago First seen · 32 lines · 58 tokens per session scan A 4837f868f109
db-backup-restore is a skill published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 400 once invoked, about $0.0003 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-31.
Other skills, from other repositories
safe-sql-execution
Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint…
studio-e2e-tests
Write and run Playwright E2E tests for Supabase Studio (e2e/studio). Use when asked to run e2e tests, write new E2E tests, or debug flaky or failing Playwright tests. Covers running commands, avoiding race conditions, waiting strategies, selectors, helper functions, and CI vs local differences.
studio-queries
React Query conventions for data fetching in Supabase Studio. Use when writing or reviewing query hooks, mutation hooks, or query keys in apps/studio/data/ — including adding the first fetch or mutation for a new API endpoint or resource. Covers queryOptions pattern, keys.ts structure, mutation hook template, and…
upgrading-chart
Upgrades Helm chart dependencies (PostgreSQL, Vault) in the Chainloop project, including vendorized charts, container images, and CI/CD workflows. Use when the user mentions upgrading Helm charts, Bitnami dependencies, PostgreSQL chart, or Vault chart. CRITICAL - Major version upgrades are FORBIDDEN and must be…
payload-cms
Install and wire Payload CMS into this Next.js 16 app, backed by Supabase Postgres and Supabase Storage — packages, payload.config.ts, the (payload) route group, collections derived from the actual page views, type generation, migrations, and proving the read loop end-to-end. Use when the user asks to "add a CMS"…
dump-schema
Dump clean Postgres schema to a file and copy path to clipboard.