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 arjunprabhulal/devops-skills --skill backup-and-restoregit clone --depth 1 https://github.com/arjunprabhulal/devops-skillsWrote 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/arjunprabhulal/devops-skills/backup-and-restore)<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/backup-and-restore"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/backup-and-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.
<a href="https://agentmods.dev/skills/arjunprabhulal/devops-skills/backup-and-restore"><img src="https://agentmods.dev/badge/skills/arjunprabhulal/devops-skills/backup-and-restore.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.00118 | $0.01450 |
| Opus 5 | $0.00059 | $0.00725 |
| Sonnet 5 | $0.00024 | $0.00290 |
| Haiku 4.5 | $0.00012 | $0.00145 |
Grade A, and why
backup-and-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 9d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backup and Restore
A backup is not a file sitting in object storage — it is a promise that you can get data back in a specific amount of time, and that promise is worthless until it has been tested. Most organizations discover their backup was broken, incomplete, or too slow to restore at the exact moment they can least afford to learn it: during an incident.
The backup job succeeding is the least interesting fact about your backup strategy. The interesting fact is whether a restore, run cold by someone who did not write the backup script, gets the right data back inside the time the business can tolerate losing it.
An untested backup is not a backup — it is an unverified hope that you will find out about during an outage.
1. Derive frequency from RPO, not from habit
Recovery Point Objective is the amount of data loss the business can tolerate, expressed as time — "we can lose 15 minutes of orders" is a real constraint, "we back up nightly because that's the default" is not. Backup frequency is a direct consequence of RPO, not an independent decision.
- State the RPO in writing for each dataset, agreed with whoever owns the business impact of losing that data, before picking a schedule.
- A nightly backup implies up to 24 hours of acceptable loss — check that against what the business actually said, not what the tooling defaults to.
- Use continuous or incremental backups (WAL shipping, binlog streaming) when the RPO is measured in minutes, since a full nightly dump cannot meet that bar.
Done when: the backup schedule for each dataset is traceable to a stated RPO, not to the tool's default interval.
2. Test restores on a schedule, not just backups
The backup job exercises one code path; the restore exercises a completely different one, and it is the one that matters during an incident. A backup that has never been restored has an unknown, not a known, recovery time.
- Run a full restore into an isolated environment on a fixed cadence — monthly is a reasonable default — and measure how long it actually takes, not how long you assumed.
- Restore the way you would during a real incident — from the actual backup artifact, by someone who is not the one who configured the job — to catch documentation gaps early.
- Track Recovery Time Objective against the measured restore time, and treat a restore that blows past RTO as a finding to fix, not a one-off.
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.
- 9d ago First seen · 120 lines · 118 tokens per session scan A f60b364be3bb
backup-and-restore is a skill published in the GitHub repository arjunprabhulal/devops-skills (3 stars, last pushed 15d ago), licensed MIT. It adds 118 tokens to every session and 1,450 once invoked, about $0.0006 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
google-mobile-ads-android-migrate-to-next-gen
Migrates Android applications from the old, legacy Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk). Provides comprehensive mapping tables for imports, classes, and method signatures to help determine…
agent-platform-inference
Connects to and performs inference with Google Cloud Agent Platform GenAI models, including First-Party Gemini models and Third-Party OpenMaaS models (Llama, DeepSeek, Qwen, etc.). Use when asked to perform inference, ask a model a question, run a test prompt, execute chat completions, or generate code for calling…
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
agent-platform-eval-flywheel
Measures and improves the quality of AI models and agents on Google Cloud using the Eval Quality Flywheel methodology. Use when evaluating an agent or model, building an eval dataset, picking or writing evaluation metrics, analyzing failures, comparing results before and after a fix, or when guidance is needed on…
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
agent-platform-deploy
Deploy open models or custom weights from Model Garden to Agent Platform endpoints, check the status of an in-progress deployment operation, or clean up resources by undeploying models and deleting endpoints. Use when asked to actively deploy a model, list the Model Garden CATALOG of available models, check if a…