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/m3talux/superbrain/migrategit clone --depth 1 https://github.com/m3talux/superbrainWhat 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.00039 | $0.01950 |
| Opus 5 | $0.00019 | $0.00975 |
| Sonnet 5 | $0.00008 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
migrate 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are running the SuperBrain /superbrain:migrate command. Your job is to fold the user's
existing Obsidian vault into SuperBrain's category structure non-destructively.
The user may have passed an argument: $ARGUMENTS.
Hard invariants — must never be violated
- The source vault is READ-ONLY. Never
Write,Edit,rm,mv, or otherwise modify any file inside the source vault. Use theReadtool only. No git operations on the source. - Never overwrite a destination note. If a destination note already exists for a different
source path, write the copy to
<basename>-<8-char-hash>.mdand record the collision in the final report. - Idempotent on re-run. A destination note whose frontmatter
migrated_frommatches the current source path counts as already migrated — skip it. So re-running this command on the same source produces no duplicates and resumes cleanly after an interruption.
Step 1 — Locate the source vault
Determine the source vault path in this priority order:
-
If
$ARGUMENTSis a non-empty path:- If it's
--dry-run(no path), setDRY_RUN=trueand continue without a path. - Otherwise: resolve it; if it's an existing directory containing an
.obsidian/folder OR at least one.mdfile at depth ≤ 2, accept it as the source. If--dry-runis also in$ARGUMENTS, setDRY_RUN=true.
- If it's
-
Otherwise, auto-detect by reading Obsidian's vault registry. The location depends on host OS:
- macOS:
~/Library/Application Support/obsidian/obsidian.json - Linux:
$XDG_CONFIG_HOME/obsidian/obsidian.jsonif set, else~/.config/obsidian/obsidian.json - Windows:
%APPDATA%\obsidian\obsidian.json(typically~/AppData/Roaming/obsidian/obsidian.json)
The file's
vaultsobject lists vaults the user has opened, each with apath. Filter to entries whosepathexists on disk. - macOS:
-
If the registry produces 0 candidates, scan these common defaults (existence check only):
- All platforms:
~/Obsidian,~/Documents/Obsidian,~/Documents/Obsidian Vault - macOS only:
~/Library/Mobile Documents/iCloud~md~obsidian/Documents/*(iCloud)
- All platforms:
-
Decision:
- 0 candidates → ask the user: "I couldn't auto-detect an Obsidian vault. Could you give me the absolute path?" Wait for a reply; validate it (directory, contains markdown).
- 1 candidate → confirm with the user: "I found
<path>— proceed with that?". Wait. - >1 candidate → present the list with brief identifiers and ask the user to pick.
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.
- 2d ago First seen · 141 lines · 39 tokens per session scan A 11cfc771c095
migrate is a command published in the GitHub repository m3talux/superbrain (41 stars, last pushed 22d ago), licensed MIT. It adds 39 tokens to every session and 1,950 once invoked, about $0.0002 per session on Opus 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
om-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.
om-vault-audit
Deep structural audit of the vault. Checks indexes, folder placement, frontmatter, links, Bases, and consistency. Fix what can be fixed, flag what needs user input.
om-incident-capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
om-intake
Process all unread meeting notes in work/meetings/ — reads each file, classifies content, routes to the right vault notes, then clears the inbox.
om-wrap-up
Full session review before ending. Review context, ways of working, files modified, consistency, and suggest improvements.
om-peer-scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.