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/fredoliveira/agents/backup-vaultnpx skills add fredoliveira/agents --skill backup-vaultgit clone --depth 1 https://github.com/fredoliveira/agentsWrote 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/fredoliveira/agents/backup-vault)<a href="https://agentmods.dev/skills/fredoliveira/agents/backup-vault"><img src="https://agentmods.dev/badge/skills/fredoliveira/agents/backup-vault.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.1 | $0.00062 | $0.00668 |
| Opus 5 | $0.00031 | $0.00334 |
| Sonnet 5 | $0.00012 | $0.00134 |
| Haiku 4.5 | $0.00006 | $0.00067 |
Grade A, and why
backup-vault 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 5d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault backup & rotation
Purpose
Keep a rolling set of zip snapshots of the vault in ~/Documents/obsidian/backups,
pruned to a grandfather-father-son (GFS) retention schedule so the backup folder
stays bounded instead of growing forever.
The actual work is done by backup.sh (next to this file) — the logic is
deterministic, so run the script rather than reimplementing it by hand.
Retention schedule
A backup is kept if any tier wants it; everything else is deleted.
| Tier | Rule |
|---|---|
| Daily | every backup from the last 14 days |
| Weekly | newest backup of each of the 5 most recent ISO weeks |
| Monthly | newest backup of each of the 12 most recent months |
| Yearly | newest backup of each of the 5 most recent years |
Tunable at the top of backup.sh (DAILY_DAYS, WEEKLY_KEEP, MONTHLY_KEEP, YEARLY_KEEP).
What gets backed up
- The full vault at
~/Documents/obsidian/umwelt, including.obsidian(themes, plugins, settings) so a restore reproduces the exact setup. - Excluded:
.DS_Store,.Trash/, and the backup directory itself. - Archives are named
umwelt-YYYY-MM-DD.zipand contain a top-levelumwelt/folder, so restoring is justunzip umwelt-<date>.zip.
Instructions
- Run the script:
bash ~/.claude/skills/backup-vault/backup.sh- Preview without changing anything:
bash .../backup.sh --dry-run - Override paths if needed:
VAULT_DIR=... BACKUP_DIR=... bash .../backup.sh
- Preview without changing anything:
- Report the summary line (how many backups were created / kept / pruned) and the resulting archive size.
The script is idempotent per day: at most one backup is created per calendar date, so it's safe to run repeatedly. Running it both creates today's snapshot and applies retention in one pass.
Notes
- This is local only. To replicate offsite,
rsyncthebackups/directory to the remote target after running the script, e.g.rsync -a --delete ~/Documents/obsidian/backups/ <remote>:obsidian-backups/. Because retention deletes files locally, use--deleteso the remote mirrors the same pruned set. - For unattended daily runs, schedule the script (launchd/cron, or the
/scheduleskill). Nothing in the script needs an interactive session.
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.
- 5d ago First seen · 62 lines · 62 tokens per session scan A 03d9d045ee82
backup-vault is a skill published in the GitHub repository fredoliveira/agents (24 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 668 once invoked, about $0.0003 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
create-custom-grader
Use when converting an existing benchmark, rubric, verifier, task YAML/JSON, or domain check into SkillEvaluator BYOG/BYOT custom evaluation.
simple
Summarize short user notes into clear action items.
agent-ready-cloudflare
Audit and improve website readiness for AI agents using the Cloudflare "Is It Agent Ready?" scanner (isitagentready.com). Covers scanning via API, interpreting results, generating implementation prompts, and fixing every check. Use when the user mentions "agent ready", "isitagentready", "AI agent scan", "agent…
aidlc-master
Runs the AWS AI-DLC (AI-Driven Development Life Cycle) methodology end to end: an adaptive three-phase workflow (Inception → Construction → Operations) with human approval gates, a full audit trail, and all artifacts in aidlc-docs/. Use when the user says "Using AI-DLC", "AI-DLC", "AIDLC", "aidlc-master", or asks for…
slop-eval
Objectively evaluate a UI/web design against the pols.dev anti-slop design law: detect catalogued slop tells with cited evidence, score 8 weighted axes (color, type, components, layout, motion, execution, signature, cohesion), and emit a Slop Report with a 0–100 Slop Index and grade. Use when the user asks to…
ralph-loop-kiro-specs
Automated iterative agent runner for spec-based development in Kiro. Wraps kiro-cli in a self-correcting bash loop that picks up tasks from a Kiro spec, implements them one at a time, verifies against exit criteria, and accumulates corrections and codebase patterns across iterations. Use this skill when the user…