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 sawrus/agent-guides --skill backup-restoregit clone --depth 1 https://github.com/sawrus/agent-guidesWrote 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/sawrus/agent-guides/backup-restore)<a href="https://agentmods.dev/skills/sawrus/agent-guides/backup-restore"><img src="https://agentmods.dev/badge/skills/sawrus/agent-guides/backup-restore.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01681 |
| Opus 5 | $0.00018 | $0.00840 |
| Sonnet 5 | $0.00007 | $0.00336 |
| Haiku 4.5 | $0.00004 | $0.00168 |
Grade A, and why
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 8d 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Backup & Restore
Expertise: pgBackRest full/WAL/incremental backup, PITR, S3/MinIO storage, CronJob scheduling, CloudNativePG backup CRDs.
When to load
When configuring backup infrastructure, running a restore, verifying backup integrity, or recovering from data loss.
pgBackRest Configuration
# /etc/pgbackrest/pgbackrest.conf
[global]
repo1-type=s3
repo1-path=/postgres-backups
repo1-s3-bucket=mycompany-db-backups
repo1-s3-endpoint=s3.eu-west-1.amazonaws.com
repo1-s3-region=eu-west-1
repo1-s3-key=<AWS_ACCESS_KEY>
repo1-s3-key-secret=<AWS_SECRET_KEY>
repo1-cipher-type=aes-256-cbc
repo1-cipher-pass=<STRONG_PASSPHRASE> # rotate annually
repo1-retention-full=4 # keep 4 full backups
repo1-retention-diff=14 # keep 14 differential backups
[global:archive-push]
compress-level=3
[production-db]
pg1-path=/var/lib/postgresql/data
pg1-host=postgres-primary
pg1-host-user=postgres
PostgreSQL: Enable WAL Archiving
-- postgresql.conf (or via ALTER SYSTEM)
ALTER SYSTEM SET wal_level = replica;
ALTER SYSTEM SET archive_mode = on;
ALTER SYSTEM SET archive_command = 'pgbackrest --stanza=production-db archive-push %p';
ALTER SYSTEM SET archive_timeout = '300'; -- archive segment at least every 5 min
SELECT pg_reload_conf();
Backup Commands
# Initialize stanza (run once)
pgbackrest --stanza=production-db stanza-create
# Full backup (schedule: weekly)
pgbackrest --stanza=production-db --type=full backup
# Differential backup (changes since last full — schedule: daily)
pgbackrest --stanza=production-db --type=diff backup
# Incremental backup (changes since last backup — schedule: hourly)
pgbackrest --stanza=production-db --type=incr backup
# Check backup catalog
pgbackrest --stanza=production-db info
# Verify backup integrity (reads and checksums)
pgbackrest --stanza=production-db --set=<backup-label> check
PITR Restore (Point-in-Time Recovery)
# PITR to specific timestamp (e.g., 1 minute before accidental DELETE)
# Step 1: Stop PostgreSQL
systemctl stop postgresql
# Step 2: Restore
pgbackrest --stanza=production-db \
--delta \
--target="2024-11-15 03:40:00+00" \
--target-action=promote \
--target-timeline=current \
restore
# Step 3: Start PostgreSQL in recovery mode
systemctl start postgresql
# Step 4: Monitor recovery progress
tail -f /var/log/postgresql/postgresql.log
# Watch for: "recovery stopping before commit of transaction"
# Then: "database system is ready to accept connections"
# Step 5: Verify data integrity
psql -c "SELECT count(*) FROM orders WHERE created_at > '2024-11-15 03:39:00';"
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.
- 8d ago First seen · 227 lines · 36 tokens per session scan A cb88439db2a5
backup-restore is a skill published in the GitHub repository sawrus/agent-guides (17 stars, last pushed 7d ago), licensed MIT. It adds 36 tokens to every session and 1,681 once invoked, about $0.0002 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-30.
Other skills, from other repositories
cockroachdb
CockroachDB distributed SQL database. Use for geo-distributed data.
postgresql
PostgreSQL relational database with JSONB, CTEs, window functions, and extensions. Use for SQL queries.
supabase
Supabase PostgreSQL backend-as-a-service with realtime. Use for serverless PostgreSQL.
cosmosdb
Azure Cosmos DB multi-model database with global distribution. Use for Azure.
neon
Neon serverless PostgreSQL with branching. Use for serverless Postgres.
timescaledb
TimescaleDB PostgreSQL for time-series. Use for time-series on Postgres.