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/michael-ovo/obsidian-knowledge-agent/helpgit clone --depth 1 https://github.com/Michael-OvO/obsidian-knowledge-agentWrote 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/michael-ovo/obsidian-knowledge-agent/help)<a href="https://agentmods.dev/commands/michael-ovo/obsidian-knowledge-agent/help"><img src="https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/help.svg" alt="Measured on agentmods" 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 | $0.00017 | $0.00606 |
| Opus 5 | $0.00009 | $0.00303 |
| Sonnet 5 | $0.00003 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
help 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 4d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
If $ARGUMENTS names a specific command, explain THAT command in depth — what it does,
when to reach for it, and a worked example — then stop. Otherwise present this guide,
clean and skimmable (keep the grouping and the examples):
Obsidian Knowledge Agent — what I can do
I turn anything — a link, a stray thought, a PDF, a whole syllabus — into notes worth keeping, and I learn your vault's conventions as we go. Talk to me naturally ("save this", "research X", "organize my inbox") or use a command:
▸ Start here
/obsidian-knowledge:setup— set this folder up as a vault. Adapts: scaffolds an empty folder, or adopts an existing vault and fills only the gaps./obsidian-knowledge:help [command]— this guide. Add a name for detail, e.g.… :help research.
▸ Capture & build
/obsidian-knowledge:capture <thing>— save one quick, clean note. e.g.:capture https://arxiv.org/abs/1706.03762/obsidian-knowledge:ingest [what]— build notes fromInbox/(or what you point at) at the right depth./obsidian-knowledge:research <topic>— research from the web and write teaching notes with sources. e.g.:research how RoPE positional encoding works/obsidian-knowledge:log <text>— append a timestamped line to today's daily log.
▸ Improve & maintain
/obsidian-knowledge:polish [note|folder]— improve existing notes in place (defaults to recently changed)./obsidian-knowledge:refactor <change>— reorganize safely and rewire links. e.g.:refactor split the Transformers note/obsidian-knowledge:doctor [folder]— health check: broken links, orphans, missing frontmatter./obsidian-knowledge:clean [message]— commit changed notes, clear processed Inbox (with approval), push.
▸ Learn (I improve myself)
/obsidian-knowledge:reflect— capture lessons from recent work and propose rule updates./obsidian-knowledge:evolve— review and approve my proposed rule changes.
Try this first: :setup → drop a source in Inbox/ → :ingest → :polish → :reflect.
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.
- 4d ago First seen · 39 lines · 17 tokens per session scan A 7da46988cffb
help is a command published in the GitHub repository Michael-OvO/obsidian-knowledge-agent (207 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 606 once invoked, about $0.0001 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
test-live
Execute comprehensive real-world testing of Basic Memory using the installed version. All test results are recorded as notes in a dedicated test project.
inject
Inject freeform text into the SuperBrain vault. SuperBrain splits multi-topic input, places each item in the right scope (project / decision / capture / etc.), links related notes, and updates today's daily note. Short single-blob input is preserved verbatim; longer or multi-paragraph input is split via the inject…
memory-update
Run the Memory Update protocol. Checks whether decisions, questions, assumptions, risks, tasks, or opportunities emerged in the current task and writes them to the right files, then prints the required end-of-task summary.
adopt
Adopt an existing directory as the SuperBrain vault (marks it, indexes existing notes).
migrate
Import an existing Obsidian vault into SuperBrain's structure — non-destructive (source is read-only; SuperBrain's vault gets copies). Optional path argument; otherwise Claude finds the vault.
knowledge-transfer
Interview a person to capture their operating know-how (tacit knowledge) and write it into the workspace as the company brain: processes, rules with source, glossary, decisions and open questions. For onboarding, a key person leaving, or standardizing a process.