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.
git 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/plugins/owrede/vault-memory/vmem)<a href="https://agentmods.dev/plugins/owrede/vault-memory/vmem"><img src="https://agentmods.dev/badge/plugins/owrede/vault-memory/vmem/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/plugins/owrede/vault-memory/vmem"><img src="https://agentmods.dev/badge/plugins/owrede/vault-memory/vmem.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vmem 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 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.
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.
What it actually says
{
"$schema": "https://anthropic.com/claude-code/plugin.schema.json",
"name": "vmem",
"version": "0.3.11",
"description": "Local-first agentic memory layer for Obsidian — install, diagnose, and reindex vault-memory from Claude Code via /vmem:install, /vmem:health, /vmem:reindex.",
"author": {
"name": "Oliver Wrede",
"email": "[email protected]",
"url": "https://github.com/owrede"
},
"homepage": "https://github.com/owrede/vault-memory",
"license": "MIT",
"keywords": [
"vault-memory",
"obsidian",
"mcp",
"agentic-memory",
"vmem"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 246 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 21 lines scan A 8b37e0d44fda
vmem is a plugin published in the GitHub repository owrede/vault-memory (0 stars, last pushed 13d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
open-knowledge-vault
Create and maintain portable Open Knowledge Format vaults with optional Obsidian and Dataview views.
knowledge-and-memory
Research methodology, corpus search, persistent memory, iterative workflows, and project knowledge management.
pai
Personal AI Infrastructure — persistent memory, session continuity, and knowledge graph for Claude Code.
tree-ring-memory
Local-first memory lifecycle, project bootstrap, and receipt-backed harness guidance for Claude Code using Tree Ring Memory v0.15+.
claude-mega-brain
OKF-powered knowledge context for Claude Code — injects your project knowledge base at every session.
vault-template
Personal Knowledge Management system for Obsidian with AI-powered workflows, goal tracking, and productivity coaching.