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 tonydzi/second-brain-starter-kit --skill obsidian-backupgit clone --depth 1 https://github.com/tonydzi/second-brain-starter-kitWrote 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/tonydzi/second-brain-starter-kit/obsidian-backup)<a href="https://agentmods.dev/skills/tonydzi/second-brain-starter-kit/obsidian-backup"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/obsidian-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/skills/tonydzi/second-brain-starter-kit/obsidian-backup"><img src="https://agentmods.dev/badge/skills/tonydzi/second-brain-starter-kit/obsidian-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.00081 | $0.02203 |
| Opus 5 | $0.00041 | $0.01102 |
| Sonnet 5 | $0.00016 | $0.00441 |
| Haiku 4.5 | $0.00008 | $0.00220 |
Grade A, and why
obsidian-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 3d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Obsidian backup & restore (data-safety runbook)
🧒 When reporting to Anton: always end with a child-simple "In plain words" recap in his language (plain words, no jargon) — his standing request. See memory
eli5-always.
This skill is the operational runbook for Anton's vault data-safety system. The rules (always preserve originals; always back up offsite to Google Drive) live in memory — preserve-originals-rule, vault-offsite-backup — and in the import skills (obsidian-ingest Rule 0, telegram-reimport Step 0). Don't re-derive or duplicate them here. This file says what to run, where things are, and how to recover.
The system at a glance — 4 layers
- Originals (Rule 0). Every import's raw source is copied verbatim to
$OBSIDIAN_ROOT/_originals/<key>\<date>__<name>\(sha256 manifest), never deleted. Script:archive_original.py. - 3-2-1 backup. Vault → one git bundle (full history) +
_originalscopy-only → to Google Drive (offsite/cloud) and<LOCAL_BACKUP_DIR>(separate disk). Script:backup_to_drive.py. - Nightly automation. Windows Task Scheduler job
Obsidian Backup to Driveruns the backup daily 03:00 (runs even when Claude is closed). - Weekly watchdog. Claude routine
obsidian-backup-healthcheck(Mon ~10:00) runsbackup_healthcheck.pyand Telegrams Anton — heartbeat if fine, alert (and may self-heal) if broken.
Where everything is (this machine)
| Thing | Path |
|---|---|
| Vault (git repo) | $OBSIDIAN_VAULT |
| Originals (permanent) | $OBSIDIAN_ROOT/_originals/ (+ README.txt) |
| Scripts | $IMPORTS_ROOT/{archive_original,backup_to_drive,backup_healthcheck}.py (+ backup_to_drive.cmd, log backup_to_drive.log, verdicts in backup_health\) |
| Offsite copy (cloud) | <GDRIVE_ROOT>\Obsidian-Backup\ — Google account [email protected] (G: shortcut → this folder; Google uploads to cloud) |
| Local copy (2nd disk) | <LOCAL_BACKUP_DIR>\ |
| Each copy holds | vault\Owner-Knowledge-<date>.bundle (last 14 kept) · _originals\ · MIGRATE.md · last-backup.txt |
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.
- 3d ago First seen · 127 lines · 81 tokens per session scan A d5607f0a42f3
obsidian-backup is a skill published in the GitHub repository tonydzi/second-brain-starter-kit (6 stars, last pushed 3d ago), licensed MIT. It adds 81 tokens to every session and 2,203 once invoked, about $0.0004 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-09-09.
Other skills, from other repositories
wiki-ingest
Ingest supplied source material into an Obsidian vault with provenance and claim tracking: pasted text, files staged in the selected vault's inbox or .raw archive, or explicitly approved URLs. Use for a single source or bounded batch, not for saving an assistant answer. Triggers: ingest, ingest this file, ingest this…
autoresearch
Run a bounded, source-grounded research loop, draft a cited dossier, and optionally propose a separately reviewed canonical vault merge. Use when the user wants autonomous or deep research that may access the public web. Triggers: /autoresearch, autoresearch, research this topic, deep dive into, investigate, find…
canvas
Create, inspect, and update Obsidian JSON Canvas boards with text, file, link, group, and edge nodes. Use for canvas status, canvas lists, visual maps, zones, spatial layouts, adding vault notes or media to a .canvas file, and requests such as create canvas, add to canvas, or put this on the canvas.
defuddle
Plan and, with explicit network consent, use an optional external Defuddle cleaner to extract article-like HTTPS pages as Markdown. Use for defuddle, clean this URL, strip page clutter, readable Markdown from a web page, or preparing a web source for later wiki ingestion.
obsidian-bases
Explain, draft, and validate Obsidian Bases .base files with filters, formulas, properties, summaries, and table, card, or list views. Use for Obsidian Bases, database-like vault views, dynamic tables, reading lists, task trackers, filters, formulas, summaries, and .base file edits.
obsidian-markdown
Explain, draft, or validate Obsidian Flavored Markdown syntax: properties, wikilinks, embeds, callouts, tags, comments, highlights, block references, math, and Mermaid. Use when the user explicitly requests Obsidian note formatting or syntax help, not for general Markdown or broad vault operations.