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 tahirraufkeeyu/software-development-agent-stack--sdas --skill backup-strategygit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/tahirraufkeeyu/software-development-agent-stack--sdas/backup-strategy)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/backup-strategy"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/backup-strategy/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/tahirraufkeeyu/software-development-agent-stack--sdas/backup-strategy"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/backup-strategy.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.00091 | $0.02943 |
| Opus 5 | $0.00046 | $0.01471 |
| Sonnet 5 | $0.00018 | $0.00589 |
| Haiku 4.5 | $0.00009 | $0.00294 |
Grade A, and why
backup-strategy 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- User says "we need backups", "audit our backups", "set up Velero", "our RDS snapshots aren't tested", "what's our RTO", or describes a ransomware / accidental-delete scare.
- A new data-bearing workload is being introduced (new Postgres, new bucket).
- SOC 2 / ISO 27001 evidence required for the backup control.
- A restore has never been tested in anger.
- A workload's RPO/RTO is unknown or out of date.
Do not use this skill for log retention (see log-aggregation), for metrics retention (see monitoring-setup), or for source-code backups (that is what your Git host and a periodic repo mirror cover).
Inputs
- Inventory of data-bearing systems: databases (engine, version, size), buckets (S3/GCS/Azure, size), K8s clusters (namespaces with persistent state), managed services (ElastiCache, MSK, etc.).
- Business tiering: which workloads are Tier 1 (customer-facing, payments), Tier 2 (internal critical), Tier 3 (nice-to-have).
- Target RPO / RTO per tier (defaults below).
- Regulatory constraints: data residency, retention minimums, encryption-at-rest requirements.
- Offsite destination (cross-region bucket, different cloud, or physical tape vault).
Default tiering (override with user input):
| Tier | Example workloads | RPO | RTO | Frequency | Retention |
|---|---|---|---|---|---|
| 1 | prod DB, payment bucket | 5 min | 1 h | Continuous WAL + 15-min snapshots | 30d + 7y PIT |
| 2 | prod K8s state, internal DBs | 1 h | 4 h | Hourly snapshots | 30d |
| 3 | dev, stage, analytics | 24 h | 24 h | Daily | 14d |
Outputs
- Backup inventory table with:
workload | tier | RPO | RTO | method | destination | encryption | schedule | retention | last restore test. - Scheduled jobs / resources:
- Velero
Scheduleresources for each K8s namespace group. - RDS / Aurora automated backups and cross-region snapshot copy.
- Postgres
pgBackRestorwal-gconfig for self-managed instances (logicalpg_dumpnightly + physical continuous WAL). - Bucket replication rules (S3 Cross-Region Replication, GCS dual-region, or Azure GRS).
- Velero
- Encryption posture per backup: KMS key ID, algorithm, rotation cadence.
- Access policy: who can read backups, who can delete, object-lock / MFA-delete setup.
- A restore-test calendar: monthly sample restore, quarterly full restore per tier.
- The checklist from references/backup-checklist.md, filled in.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 221 lines · 91 tokens per session scan A 0f3429a98e57
backup-strategy is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 91 tokens to every session and 2,943 once invoked, about $0.0005 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
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…