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/jansenanalytics/claudex/backup-restorenpx skills add JansenAnalytics/claudex --skill backup-restoregit clone --depth 1 https://github.com/JansenAnalytics/claudexWrote 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/jansenanalytics/claudex/backup-restore)<a href="https://agentmods.dev/skills/jansenanalytics/claudex/backup-restore"><img src="https://agentmods.dev/badge/skills/jansenanalytics/claudex/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.00039 | $0.00503 |
| Opus 5 | $0.00019 | $0.00251 |
| Sonnet 5 | $0.00008 | $0.00101 |
| Haiku 4.5 | $0.00004 | $0.00050 |
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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
backup-restore
Automated backup strategies: database dumps, file snapshots, incremental backups, verification, disaster recovery. Use when: setting up backup schedules, creating database backups, restoring from backups, verifying backup integrity, or planning disaster recovery.
Workflows
Create a backup
bash scripts/backup.sh --type <pg|sqlite|files> --source <path-or-db> --dest <backup-dir>
Creates timestamped, compressed backups. Supports PostgreSQL, SQLite, and file directories.
Restore from backup
bash scripts/restore.sh --type <pg|sqlite|files> --backup <backup-file> --dest <target>
Restores from a backup archive. Prompts for confirmation before overwriting.
Verify backup integrity
bash scripts/verify-backup.sh <backup-file>
Checks checksums, tests archive integrity, and validates contents.
Clean up old backups (retention)
bash scripts/retention-cleanup.sh <backup-dir> [--keep-days 30] [--keep-count 10]
Removes old backups based on age or count, keeping minimum required.
Set up cron schedule
bash scripts/cron-setup.sh --schedule "0 2 * * *" --command "bash /path/to/backup.sh ..."
Adds a cron entry for automated backups.
Scripts
| Script | Purpose |
|---|---|
scripts/backup.sh |
Universal backup (pg/sqlite/files) |
scripts/restore.sh |
Restore from backup |
scripts/verify-backup.sh |
Verify backup integrity |
scripts/retention-cleanup.sh |
Clean old backups |
scripts/cron-setup.sh |
Set up cron schedule |
References
| File | Contents |
|---|---|
references/backup-strategies.md |
3-2-1 rule, patterns, restore testing |
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.
- 4d ago First seen · 70 lines · 39 tokens per session scan A f40f773f8258
backup-restore is a skill published in the GitHub repository JansenAnalytics/claudex (5 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 503 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-31.
Other skills, from other repositories
backups
Use when designing or auditing a backup-and-restore program that must survive a real disaster: setting defensible RPO/RTO targets, laying out 3-2-1-1-0 copies that are offsite and immutable, wiring point-in-time recovery, and proving restores work on a schedule. NOT tuning Postgres internals or writing the…
cis-aws-database-2.8
Ensure Automatic Backups and Retention Policies are configured.
data-backup-patterns
Implement reliable data backup and recovery strategies with automated scheduling, encryption, rotation policies, and disaster recovery testing. Covers database backups, file system snapshots, and cloud storage patterns. Triggers on backup strategy, disaster recovery, or data protection requests.
mimic-eicu-mapping
Map equivalent concepts between MIMIC-IV and eICU databases. Use for multi-database studies, external validation, or understanding structural differences between databases.
mimic-table-relationships
Understand MIMIC-IV table relationships, join patterns, and identifier hierarchy. Use for correct data linkage, avoiding duplicates, and proper temporal joins.
backup-manager
Backup and restore application data (database, config, memory, skills) with ZIP archives.