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 commands/breferrari/obsidian-mind/om-vault-upgradegit clone --depth 1 https://github.com/breferrari/obsidian-mindWhat 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.00000 | $0.02654 |
| Opus 5 | $0.00000 | $0.01327 |
| Sonnet 5 | $0.00000 | $0.00531 |
| Haiku 4.5 | $0.00000 | $0.00265 |
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 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.
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, 40 lines differ
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vault Upgrade
Import and migrate content from an existing Obsidian vault into this obsidian-mind instance. Works with older obsidian-mind versions and arbitrary Obsidian vaults.
When to use: After downloading or cloning the latest obsidian-mind template, to pull in your existing vault content. Also works for migrating any Obsidian vault into the obsidian-mind structure.
Usage
/om-vault-upgrade <path-to-source-vault>
/om-vault-upgrade <path-to-source-vault> --dry-run
/om-vault-upgrade --source <path-to-source-vault>
/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— generate the migration plan without executing it (saves tothinking/)
Subagents
vault-migrator— classifies files (for arbitrary vaults) and executes the approved migration plan
Workflow
1. Validate & Detect
- Parse the source vault path from the user's input. Resolve relative paths.
- Verify the source path exists and is different from the current vault.
- Verify the source path contains
.mdfiles (is it actually a vault?). - Check for
vault-manifest.jsonin the source:- Found: read version directly. This is a known obsidian-mind vault.
- Not found: run version fingerprint detection from the target's
vault-manifest.json:- Check for
claude/Memories.mdwithoutbrain/→ v1 - Check for
brain/+bases/without.claude/agents/→ v2 - Check for
.claude/agents/→ v3.x (refine by checking for specific files) - None match → arbitrary vault (not from obsidian-mind)
- Check for
- For arbitrary vaults, also detect the vault's organizational pattern (PARA, Zettelkasten, daily notes, flat, MOC-based, inbox). This shapes how the classifier interprets folder structure. Common patterns:
- PARA:
Projects/+Areas/+Resources/+Archive/ - Zettelkasten:
Permanent/+Fleeting/+Literature/, or many numeric-ID filenames - Daily Notes:
daily/orjournal/folder with date-named files - Flat: 80%+ of files in vault root
- MOC-based: files named
MOC - *.mdorIndex - *.md
- PARA:
- Report detection result to the user: "Detected obsidian-mind v2" or "This looks like a PARA-organized Obsidian vault — I'll map Projects → work/active, Resources → reference, etc." or "This is a flat vault with no folder structure — I'll classify each note by its content."
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 · 187 lines · 0 tokens per session scan A 62ec81b06025
om-vault-upgrade is a command published in the GitHub repository breferrari/obsidian-mind (4,586 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,654 tokens. 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
session-stop
Stop recording and save this agent session to the project ledger.
ox-prime
Load SageOx team context for this AI coworker session.
ox-session-resume
belongs in the ox CLI JSON output (guidance field), not here. Skills are agent-specific wrappers; ox serves all agents (Codex, etc.). --> Resume a previously suspended session recording. Closes the open pause range; the suspended interval will be excluded from upload at stop time.
ox-agents
List available expert coworker agents and their specialties.
okf
Command "okf" from kimsanguine/llm-brain, covering 인자 파싱, 기본 private export, 🔴 share-ready gate (외부 공유 전 one-way door), legacy step 1: private dry-run 검토 and legacy step 2: private export.
pdf-to-wiki
Drive에 있는 대용량 PDF를 NotebookLM에 외주화하여 분석하고, 결과를 OUTPUTDIR에 Obsidian 노트로 저장한다.