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-updategit 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-update)<a href="https://agentmods.dev/skills/owrede/vault-memory/vm-update"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/vm-update/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-update"><img src="https://agentmods.dev/badge/skills/owrede/vault-memory/vm-update.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.00098 | $0.01449 |
| Opus 5.5 | $0.00039 | $0.00580 |
| Sonnet 5.5 | $0.00020 | $0.00290 |
| Haiku 4.5 | $0.00010 | $0.00145 |
Grade A, and why
vm-update 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.
| 3 | Fetch latest release tag from GitHub API | `curl https://api.github.com/repos/owrede/vault-memory/releases/latest`. Falls back to `VM_UPDATE_LATEST_VERSION` env var for testing / offline. | How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vm-update — Upgrade the vault-memory Obsidian plugin
Out-of-band updater for installations that were sideloaded via vm-install.
Checks GitHub Releases for a version newer than what is on disk; if a newer
release is published, downloads + verifies it and swaps it into place
atomically.
When to invoke
- User runs
/vm-update(primary trigger) - User says "update vault-memory plugin", "upgrade vault-memory", "Plugin aktualisieren"
- After a new vault-memory v2.x release lands and the user wants to pick it up
Release prerequisites
IMPORTANT: This skill queries a hard-coded GitHub Releases endpoint. Before v2.0.0 (and any subsequent release) is published, the API returns 404 — the release artifacts referenced by this skill DO NOT exist yet. They will be published during Phase 8 release prep.
Required release artifacts (publisher checklist, same as vm-install):
| Asset | Purpose |
|---|---|
vault-memory-plugin-<version>.tar.gz |
Plugin tarball with manifest.json, main.js, styles.css, versions.json at the archive root |
manifest.sha256 |
Single-line SHA-256 hex digest of the tarball |
The release URL template is set via the RELEASE_URL_PLACEHOLDER constant
near the top of update.sh. The constant is marked with a # TODO: replace placeholder before publishing comment. The latest release lookup uses
https://api.github.com/repos/owrede/vault-memory/releases/latest; override
the tarball + checksum URLs at test time via VM_UPDATE_RELEASE_URL and
VM_UPDATE_SHA256_URL, and override the release-version lookup itself via
VM_UPDATE_LATEST_VERSION.
When to invoke
- User runs
/vm-update(primary trigger) - User says "update vault-memory plugin", "upgrade vault-memory", "Plugin aktualisieren"
- After a new vault-memory v2.x release lands
What this skill does
7 idempotent checkpoints mirroring vm-install, scoped to the update path.
| # | Checkpoint | Action |
|---|---|---|
| 1 | Discover Obsidian vault | Same logic as vm-install. Honors VAULT_PATH. |
| 2 | Read installed manifest.json.version |
Parse <vault>/.obsidian/plugins/vault-memory/manifest.json. If missing, abort with "Plugin not installed — run /vm-install first." |
| 3 | Fetch latest release tag from GitHub API | curl https://api.github.com/repos/owrede/vault-memory/releases/latest. Falls back to VM_UPDATE_LATEST_VERSION env var for testing / offline. |
| 4 | Compare versions (semver) | If installed >= latest → exit 0 with "Already up to date". |
| 5 | Download + verify SHA-256 | Same atomic flow as vm-install (download → checksum → mismatch aborts before extraction). |
| 6 | Atomic replace | Extract into .NEW, swap in via mv, delete .OLD. Failure leaves the prior install intact. |
| 7 | Prompt user to reload | Print: "Reload Obsidian (Cmd+R / Ctrl+R) or disable+enable the plugin in Settings → Community Plugins to pick up the upgrade." |
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 · 112 lines · 98 tokens per session scan A c26324483dfe
vm-update is a skill published in the GitHub repository owrede/vault-memory (0 stars, last pushed 13d ago), licensed MIT. It adds 98 tokens to every session and 1,449 once invoked, about $0.0004 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.