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 pssah4/vault-operator --skill vault-health-batchgit clone --depth 1 https://github.com/pssah4/vault-operatorWrote 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/pssah4/vault-operator/vault-health-batch)<a href="https://agentmods.dev/skills/pssah4/vault-operator/vault-health-batch"><img src="https://agentmods.dev/badge/skills/pssah4/vault-operator/vault-health-batch/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/pssah4/vault-operator/vault-health-batch"><img src="https://agentmods.dev/badge/skills/pssah4/vault-operator/vault-health-batch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00032 | $0.01097 |
| Opus 5 | $0.00016 | $0.00549 |
| Sonnet 5 | $0.00006 | $0.00219 |
| Haiku 4.5 | $0.00003 | $0.00110 |
Grade A, and why
vault-health-batch 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 10d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Health Batch Mode
You work through Vault Health findings AUTONOMOUSLY in batches. Ask the user ONLY at real decision points, NOT on every single fix. All changes are reversible via the undo bar (checkpoints are created automatically).
Phase 1: TRIAGE
- Call
vault_health_check - Read the findings and group them by type
- Give the user a short overview (3-5 lines):
Vault Health: X findings - N orphaned notes (M of them with context) - N missing backlinks - N broken links - N inconsistent tags - N weak clusters I will start with the mechanical fixes (backlinks, tags). For broken links and isolated orphans I will ask you. - Start Phase 2 IMMEDIATELY -- do NOT wait for confirmation
Phase 2: BATCH FIX
Work through the types in this order.
2a: Missing backlinks + orphans with context (ONE TOOL CALL)
These are mechanical fixes: entities that are referenced but do not link back.
Steps:
- Call
vault_health_checkwithaction: "fix_backlinks" - The tool fixes ALL missing backlinks in one batch (pure code, 0 LLM cost)
- Show the user the result: "X entities updated, Y backlinks added"
NO read_file, NO update_frontmatter, NO sub-agent. ONE tool call does everything.
2c: Inconsistent tags (AUTONOMOUS)
Tags that differ only in upper/lower case.
Steps:
- Pick the more frequent variant
- Change all occurrences of the rarer variant via
update_frontmatter - NO questions
2d: Broken links (USER DECISION)
Links that point to notes that do not exist.
Steps:
- Show ALL broken links together (not one by one)
- STOP -- ask the user:
N broken links found: - [[Note A]] (referenced by 3 notes) - [[Note B]] (referenced by 1 note) Options: a) Create stub notes (with basic content) b) Remove the links c) Decide one by one d) Skip - Continue only after the answer
2e: Orphaned notes WITHOUT context (USER DECISION)
Completely isolated notes without any MOC links.
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.
- 10d ago First seen · 143 lines · 32 tokens per session scan A bab56a3a3249
vault-health-batch is a skill published in the GitHub repository pssah4/vault-operator (249 stars, last pushed 9d ago), licensed Apache-2.0. It adds 32 tokens to every session and 1,097 once invoked, about $0.0002 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
wiki-retrieve
Build and query a vault-local contextual BM25 retrieval index with optional multilingual Nomic cosine reranking; use for retrieve, hybrid retrieval, BM25, rerank, contextual retrieval, chunk search, vault search, semantic search, find relevant passages, or retrieval diagnostics. Derived caches stay under .vault-meta…
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.
save
Save a user-selected answer, decision, insight, or session summary into an Obsidian vault as one reviewed transaction. Use only when the user explicitly asks to preserve specific conversation content, not when they supply a file or URL to ingest. Triggers: /save, save this, save that answer, file this conversation…
wiki-fold
Create a bounded, extractive, structurally idempotent rollup of recent Obsidian wiki log entries, with dry-run preview by default and one optional transaction apply. Use for manual log compression without modifying child pages. Triggers: fold the log, run a fold, run wiki-fold, log rollup, roll up log entries, commit…
wiki-mode
Read or configure the vault filing methodology and suggest destinations for planned knowledge creation under Generic, LYT, PARA, or Zettelkasten. Use for wiki mode, methodology mode, what is my vault mode, set vault mode, switch to PARA, use LYT, Zettelkasten setup, change mode, configure mode, or methodology routing.…
wiki-cli
Detect and use the official Obsidian command-line interface for read-only vault access; use for wiki-cli, Obsidian CLI, Obsidian read, Obsidian search, vault transport, which transport, transport detection, backlinks, tags, or Obsidian command line. Mutations always go through the claude-obsidian transaction core.