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/add-vaultnpx skills add owrede/vault-memory --skill add-vaultgit 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/add-vault)<a href="https://agentmods.dev/skills/owrede/vault-memory/add-vault"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/add-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 | $0.00092 | $0.00839 |
| Opus 5 | $0.00046 | $0.00419 |
| Sonnet 5 | $0.00018 | $0.00168 |
| Haiku 4.5 | $0.00009 | $0.00084 |
Grade A, and why
add-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 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Vault
One-shot onboarding for an additional Obsidian vault. After this skill runs, the user can open that vault in Claude Code and immediately have the vault-memory MCP tools available.
Trigger
- User invokes
/add-vault - User says "add this vault to memory", "register this vault", "neuer vault einrichten"
- User opens Claude Code in a vault directory and the
mcp__vault-memory__*tools are missing or returning empty
Prerequisites
vault-memory must already be installed system-wide. If not, run /install-vault-memory first.
Check via:
which vault-memory
If missing: stop and tell the user to run /install-vault-memory. Do not try to install anything else from this skill.
Behavior
Detect the vault path:
- If the user passed an explicit path argument (
/add-vault /path/to/vault), use that. - If they invoked the skill from inside a vault (working directory contains
.obsidian/), default to the current directory. - Otherwise, ask the user with
AskUserQuestionwhich vault they want to add.
Confirm with the user before mutating anything:
- Show the detected path, the proposed
name(slugified basename), andwrite_enabled(default false = read-only). - Confirm via
AskUserQuestion— give them the chance to override the name or enable writes.
Run the CLI:
vault-memory add-vault "<path>" [--name <name>] [--write] [--no-index]
The CLI does all three steps atomically (config.toml append, .mcp.json write/merge, initial index). It prints a per-step transcript — relay that verbatim to the user.
Default to running the index unless the user says they want to skip it (--no-index flag). For large vaults (>1000 notes), warn the user that initial indexing can take several minutes; they may want to run it in a separate terminal.
After completion, tell the user to restart Claude Code in the new vault for the MCP tools to attach.
Edge Cases
- Vault path doesn't exist: surface the CLI error verbatim, suggest checking the path.
- Vault already registered under the same path: the CLI handles this idempotently (reports "already registered"), the skill just relays it.
- Vault name collision with different path: CLI rejects with a clear error. Ask the user for an override name via
AskUserQuestion. - Vault is read-only mounted (e.g. iCloud not synced): the
.mcp.jsonwrite will fail with EACCES. Surface the error and stop.
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 · 77 lines · 92 tokens per session scan A d0d03f74f3e7
add-vault is a skill published in the GitHub repository owrede/vault-memory (0 stars, last pushed 26d ago), licensed MIT. It adds 92 tokens to every session and 839 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
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…
auditing-subgroup-fairness
Audit an OpenMed NER or de-identification model for performance disparities across demographic subgroups (sex, age band, race/ethnicity when available) using openmed.eval.fairnessreport. Use when the user wants per-subgroup recall and leakage, wants to check whether de-identification under-protects a group, wants to…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…