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/owrede/vault-memory/healthnpx skills add owrede/vault-memory --skill 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/health)<a href="https://agentmods.dev/skills/owrede/vault-memory/health"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/health.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.00095 | $0.00519 |
| Opus 5 | $0.00048 | $0.00260 |
| Sonnet 5 | $0.00019 | $0.00104 |
| Haiku 4.5 | $0.00010 | $0.00052 |
Grade A, and why
health scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Ollama | `curl /api/tags` on configured endpoint | What it actually says
/vmem:health — Diagnose vault-memory
Read-only health check across every dimension the install touches. No state is mutated.
What it checks
| Dimension | Probe |
|---|---|
| Binary | vault-memory in PATH + resolvable version |
| Ollama | curl /api/tags on configured endpoint |
| Config | ~/.vault-memory/config.toml present + count registered vaults |
| Per-vault DB | sqlite3 PRAGMA integrity_check + note count |
| WAL leftovers | .db-wal file size — warns if >4KB (uncommitted state) |
| MCP server | JSON-RPC initialize smoketest |
Output: one PASS/WARN/FAIL line per dimension. Exits 0 on PASS (WARN non-blocking), 3 if any FAIL.
How to execute
VAULT_MEMORY_DIAGNOSE=1 bash "$CLAUDE_PROJECT_DIR/.claude/skills/install/setup.sh"
Or via the bundled wrapper:
bash "$CLAUDE_PROJECT_DIR/.claude/skills/health/health.sh"
The wrapper exists so the user (or the agent) can run /vmem:health without remembering the diagnostic env var. It dispatches into install/setup.sh --diagnose.
When to use
- User says "/vmem:health", "is vault-memory healthy", "diagnose memory"
- The
mcp__vault-memory__*tools stop responding after a system update / OS upgrade - Obsidian plugin reports an error and you need to know whether the CLI side is OK
- Before filing a bug — collect the diagnostic output
Output is non-destructive
This skill never installs, never modifies config, never runs vault-memory index. To fix anything it finds, follow up with /vmem:install (for setup gaps) or /vmem:reindex (for stale indexes).
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 · 47 lines · 95 tokens per session scan A 881c400c76a7
health is a skill published in the GitHub repository owrede/vault-memory (0 stars, last pushed 27d ago), licensed MIT. It adds 95 tokens to every session and 519 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…