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 vm-installgit 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/vm-install)<a href="https://agentmods.dev/skills/owrede/vault-memory/vm-install"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/vm-install/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/vm-install"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/vm-install.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.00151 | $0.01546 |
| Opus 5.5 | $0.00060 | $0.00618 |
| Sonnet 5.5 | $0.00030 | $0.00309 |
| Haiku 4.5 | $0.00015 | $0.00155 |
Grade A, and why
vm-install 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 1mo 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.
| 2 | Download tarball | `curl --fail --location` from `RELEASE_URL_PLACEHOLDER` (or `VM_INSTALL_RELEASE_URL` override) into a temp dir. | How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vm-install — Sideload the vault-memory Obsidian plugin
The single entry point for installing the vault-memory Obsidian plugin without going through the Obsidian community plugin store. Downloads the latest v2.0.0+ release tarball from GitHub Releases, verifies it, and lands it in the user's vault.
When to invoke
- User runs
/vm-install(primary trigger) - User says "install vault-memory plugin", "set up the plugin", "Plugin installieren", "VM plugin einrichten"
- The vault-memory plugin is not visible under
<vault>/.obsidian/plugins/vault-memory/ - A fresh install on a machine where only the MCP server (CLI) is configured
Release prerequisites
IMPORTANT: This skill installs from a hard-coded GitHub Releases URL. Before v2.0.0 ships, the release artifacts referenced by this skill DO NOT exist — they will be published during Phase 8 release prep.
Required release assets (publisher checklist):
| Asset | Purpose |
|---|---|
vault-memory-plugin-<version>.tar.gz |
Plugin tarball (contains manifest.json, main.js, styles.css, versions.json at archive root) |
manifest.sha256 |
Single-line SHA-256 hex digest of the tarball |
The release URL is set via the RELEASE_URL_PLACEHOLDER constant near the
top of setup.sh. The constant is marked with a # TODO: replace placeholder before publishing comment. Until the v2.0.0 release is published, invoking
this skill will fail at the download checkpoint — point the script at a local
fixture tarball via the VM_INSTALL_RELEASE_URL environment variable for
testing.
What this skill does
The skill walks through 7 idempotent checkpoints. Each silently passes when already met, or applies a fix once.
| # | Checkpoint | Action on miss |
|---|---|---|
| 1 | Discover Obsidian vault | Probe ~/Documents/*/.obsidian, ~/Notes/.obsidian, iCloud Obsidian paths; honor VAULT_PATH env var override. If multiple vaults found, list + ask. |
| 2 | Download tarball | curl --fail --location from RELEASE_URL_PLACEHOLDER (or VM_INSTALL_RELEASE_URL override) into a temp dir. |
| 3 | Verify SHA-256 | Compute shasum -a 256 of the tarball and compare against the manifest.sha256 shipped in the same release. Mismatch → abort before extraction. |
| 4 | Extract atomically | Extract tarball into <vault>/.obsidian/plugins/vault-memory.NEW/, mv any existing dir aside to vault-memory.OLD/, mv .NEW → vault-memory, rm .OLD only on success. |
| 5 | Set plugin config flag | Add or update [plugin]\nenabled = true in ~/.vault-memory/config.toml. Create the file if missing. |
| 6 | Prompt user | Print explicit copy: "Open Obsidian → Settings → Community Plugins → Installed plugins → toggle 'vault-memory' on." |
| 7 | Done | Print success summary, log run to ~/.vault-memory/skills/vm-install.log. |
What ships with it
2 files 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.
- 1mo ago First seen · 116 lines · 151 tokens per session scan A 42ba5c42f3c7
vm-install is a skill published in the GitHub repository owrede/vault-memory (0 stars, last pushed 13d ago), licensed MIT. It adds 151 tokens to every session and 1,546 once invoked, about $0.0006 per session on Opus 5.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
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
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.