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 owrede/vault-memory --skill audit-vault-healthgit clone --depth 1 https://github.com/owrede/vault-memoryWrote 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/owrede/vault-memory/audit-vault-health)<a href="https://agentmods.dev/skills/owrede/vault-memory/audit-vault-health"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/audit-vault-health/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/owrede/vault-memory/audit-vault-health"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/audit-vault-health.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.00102 | $0.01591 |
| Opus 5 | $0.00051 | $0.00796 |
| Sonnet 5 | $0.00020 | $0.00318 |
| Haiku 4.5 | $0.00010 | $0.00159 |
Grade A, and why
audit-vault-health 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/audit-vault-health — Vault Health Audit
A read-only diagnostic that produces a structured report on five dimensions of vault hygiene. Useful before major migrations, on a quarterly cadence, or when something feels "off" but isn't pinpointable.
When to invoke
- User runs
/audit-vault-health(primary trigger) - User says "audit my vault", "check vault consistency", "vault health", "Vault-Gesundheit prüfen", "Was ist im Vault kaputt?"
- After a bulk import or migration, before relying on vault-memory search
Requirements
mcp__vault-memory__*tools available in the session- At least one vault registered
What the audit reports
The audit produces five sections, each derived from one or two MCP tool calls. Every finding is presented with a count and the top 3-5 examples so the user can decide whether to act.
1. Overview (from vault_stats)
- Vault name, path, total notes, total words, embedding model
- Last index run timestamp + "freshness" classification:
- Fresh: indexed_at within last 24h
- Stale: 1–7 days
- Cold: >7 days (recommend
vault-memory indexor trigger a save)
- Top 5 tags + count
- Top 10 frontmatter keys + count (used as schema reference in section 5)
2. Broken wikilinks (from find_broken_links)
- Total broken count
- Top 5 broken targets (paths) with backlink count for each (indicating impact)
- Categorize:
- Likely typos — broken target has a near-match in the vault (Levenshtein distance ≤ 2). Show the suggested fix.
- Likely deletions — broken target has no near-match; the target was probably moved/deleted.
- Possibly new — broken target looks like a forward-reference (e.g., a TODO note that hasn't been created yet).
3. Tag drift (from vault_stats.top_tags + custom)
Surfaces tags that are semantically the same but written differently. Heuristic: normalize each top-tag via:
norm(t) = t.toLowerCase().replace(/^#/, "").replace(/[-_\s]/g, "")
Group tags by their normalized form. Any group with >1 distinct raw form is a drift candidate.
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 · 137 lines · 102 tokens per session scan A 633d41bd0033
audit-vault-health is a skill published in the GitHub repository owrede/vault-memory (0 stars, last pushed 2d ago), licensed MIT. It adds 102 tokens to every session and 1,591 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-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
shellm
Reference for the shellm system — recursive LLM shell, identity management, memory, skills, trajectory, and all CLI tools. Use when working on shellm itself, debugging agent behavior, or understanding how the pieces fit together.