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/vm-installnpx skills add owrede/vault-memory --skill vm-installgit clone --depth 1 https://github.com/owrede/vault-memoryWhat 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.00151 | $0.01546 |
| Opus 5 | $0.00076 | $0.00773 |
| Sonnet 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 yesterday.
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.
- yesterday 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 23d ago), licensed MIT. It adds 151 tokens to every session and 1,546 once invoked, about $0.0008 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…