Obsidian Mind is an Obsidian vault that stores notes, links, indexes, and other accumulated context so AI coding agents can retain memory across sessions. It is designed for Claude Code and also supports Codex CLI and Gemini CLI through shared hooks, commands, and vault data. Its catalogue add-ons package the vault’s commands, agents, skills, hooks, instructions, settings, plugin, and MCP integration.
Borrowing it
Nothing to install: this file belongs to breferrari/obsidian-mind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/breferrari/obsidian-mind/main/.claude/commands/om-vault-upgrade.mdgit clone --depth 1 https://github.com/breferrari/obsidian-mindWrote 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/commands/breferrari/obsidian-mind/om-vault-upgrade)<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-vault-upgrade"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-vault-upgrade/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/commands/breferrari/obsidian-mind/om-vault-upgrade"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-vault-upgrade.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.00024 | $0.04308 |
| Opus 5.5 | $0.00010 | $0.01723 |
| Sonnet 5.5 | $0.00005 | $0.00862 |
| Haiku 4.5 | $0.00002 | $0.00431 |
Grade A, and why
om-vault-upgrade 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 15d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- upgrade — 92% identical, 113 lines differ
How it starts
The opening of the file, as written. The whole thing — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Upgrade
Two jobs, picked by whether a source vault is given:
- No source: upgrade THIS vault to the latest template release, through ShardMind, keeping every local improvement. See Upgrade this vault below.
- A source vault: import its content into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults. See Workflow below.
Usage
/om-vault-upgrade # upgrade this vault (ShardMind)
/om-vault-upgrade --dry-run # show the upgrade plan only
/om-vault-upgrade <path-to-source-vault> # import another vault's content
/om-vault-upgrade <path-to-source-vault> --dry-run
/om-vault-upgrade --source <path-to-source-vault> [--dry-run]
Arguments:
<path-to-source-vault>— absolute or relative path to the vault to migrate FROM (positional or via--source)--dry-run— produce the plan without changing anything
Upgrade this vault (ShardMind)
ShardMind owns the engine lifecycle: shardmind update moves a managed vault to a new release, and shardmind adopt brings a vault that was cloned without it under management. This command owns the judgment ShardMind's bulk modes cannot make: whether a file that differs from the template is one you improved (keep it, and maybe upstream it) or one you never updated (take the new version). A blunt use-all-theirs downgrades every local enhancement. A blunt keep-all-mine is worse: it records stale files as yours, so the vault reports itself up to date while those files stay old and no later update touches them.
Requires ShardMind 0.2.1 or later (shardmind --version; upgrade with npm i -g shardmind@latest). Without ShardMind, use Workflow below with this vault's previous copy as the source.
U1. Plan
node --experimental-strip-types .claude/scripts/upgrade-plan.ts
It never changes the vault. It detects which case this is:
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.
- 15d ago Changed · +4 lines · +24 tokens per session 3757e752e574
- 16d ago Changed 9555411b1995
- 17d ago Changed · +7 lines 959d94687fd1
- 23d ago Changed e0e1fb3b96cb
- 24d ago Changed · +54 lines 2ea7330c57cb
- 2mo ago First seen · 187 lines · 0 tokens per session scan A 62ec81b06025
om-vault-upgrade is a command published in the GitHub repository breferrari/obsidian-mind (5,454 stars, last pushed 12d ago), licensed MIT. It adds 24 tokens to every session and 4,308 once invoked, about $0.0001 per session on Opus 5.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-30.
Other commands, from other repositories
prime
Load SageOx team context for this AI coworker session.
session-learn
Extract knowledge from the current session. Invoke with /session-learn or "extract this session".
status
Show memex statistics and status including projects, memos, and pending items.
curate
A command for maintaining a file-based knowledge wiki. It can review pages, shorten overlong material, manage page lifecycles, find possible contradictions, and rebuild weak connections between notes.
ingest
A command for adding information to a file-based knowledge wiki from web pages, files, or text notes. It classifies the material, updates or creates wiki pages, and adds links between related pages.
init_newbrain
Onboarding interativo que personaliza AGENTS.md, Memória/ e a estrutura inicial do vault.