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.
git clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/commands/christopherlouet/claude-base/ops-backup)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-backup"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-backup/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/commands/christopherlouet/claude-base/ops-backup"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-backup.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.00000 | $0.00565 |
| Opus 5.5 | $0.00000 | $0.00226 |
| Sonnet 5.5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
ops-backup 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OPS-BACKUP Agent
Backup, restore and disaster-recovery strategy for the project's critical data.
Request context
$ARGUMENTS
Objective
Define and implement a 3-2-1 backup strategy (3 copies, 2 media, 1 offsite) with tested, documented restore procedures — and, for business continuity, a disaster-recovery (DR) plan with clear, tested RPO/RTO.
Workflow — backup & restore
- Identify the critical data to back up (DB, files, configs, logs)
- Choose the appropriate backup type (full, incremental, differential, snapshot)
- Generate backup and restore scripts for the detected stack
- Configure cron scheduling and retention
- Configure monitoring and alerts on backups
- Generate the restore procedure documentation
- Propose an RPO/RTO matrix per incident scenario
- Encrypt backups containing sensitive data
Workflow — disaster recovery (DR)
- Assess service criticality (mission critical, business critical, standard)
- Choose the DR strategy (Backup & Restore, Pilot Light, Warm Standby, Hot Standby) per target RPO/RTO
- Document the DR runbook (failover, failback, emergency contacts)
- Configure replication and cross-region backups
- Define DR tests (tabletop, simulation, full failover); generate
activate-dr.sh,validate-dr.sh,test-dr-failover.sh - Monitor DR health (replication lag, backup status, site health)
Expected output
- Scripts: backup-db.sh, backup-files.sh, restore-db.sh, test-restore.sh (+ DR: activate-dr.sh, validate-dr.sh, test-dr-failover.sh)
- Recommended cron configuration
- Restore matrix (scenario, RPO, RTO, procedure) and chosen DR strategy with runbook
- Complete backup + DR checklist
Related agents
| Before | Usage |
|---|---|
/ops:ops-database |
DB migrations and schema |
/ops:ops-infra-code |
Infrastructure backup |
| After | Usage |
|---|---|
/ops:ops-monitoring |
Backup/DR alerts |
/ops:ops-cost |
Optimize backup/DR costs |
IMPORTANT: An untested backup is not a backup. Test restores AND DR failover regularly.
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 · 64 lines · 0 tokens per session scan A 28d52acab8a1
ops-backup is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 565 tokens. 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 commands, from other repositories
migrate
Generate and manage database migrations.
scaffold
Scaffold project components from templates.
deploy
Deploy application with pre/post-deploy checks.
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
log-decision
Append an architectural decision to the persistent decision log.
session-log
Explain where session history lives now that the toolkit keeps no session log.