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/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/setup)<a href="https://agentmods.dev/commands/michael-ovo/obsidian-knowledge-agent/setup"><img src="https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/setup/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/michael-ovo/obsidian-knowledge-agent/setup"><img src="https://agentmods.dev/badge/commands/michael-ovo/obsidian-knowledge-agent/setup.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.00019 | $0.00672 |
| Opus 5.5 | $0.00008 | $0.00269 |
| Sonnet 5.5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
setup 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.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up the current folder as an Obsidian Knowledge Agent vault. Detect first, then do the least surprising thing. Always idempotent — never clobber anything that exists.
Step 0 — Detect the folder and tell me which mode you're in:
- Already a vault —
.agents/learned/exists → RESUME (don't re-scaffold). - An existing Obsidian vault — has notes / an
.obsidian/folder, but no.agents/learned/→ ADOPT (fit what's there, fill only the gaps). - Empty / new folder — no notes, no vault structure → SCAFFOLD (build a starter).
Then run the matching mode:
RESUME — it's already set up
Don't re-create anything. Report status in a couple of lines — the branches, how many
items are in Inbox/, the last journal.md entry — and route me to work:
"Inbox has 3 items — want me to :ingest? Or tell me what to capture." Stop there.
ADOPT — an existing vault (the adaptive path)
- Read, don't impose. Map the existing top-level folders, naming style, and the frontmatter on a few notes. Treat that as the vault's conventions — do not add new branch folders or rename anything.
- Fill only the gaps. Create
.agents/learned/(journal.md,conventions.md,examples.md, askills/folder) only if missing; addInbox/and aDashboard.mdmap-of-content that links the existing branches. Never overwrite existing files. - Seed conventions for review. Write what you detected (naming, frontmatter, folder
shape) into
.agents/learned/conventions.mdas a proposed starting point, and show me the diff before committing it. - Commit the additions, then point me at
/obsidian-knowledge:help.
SCAFFOLD — an empty folder
- Branches. Create top-level branch folders — from
$ARGUMENTSif given, otherwise propose a small default (a sharedReferences/plus one or two domains) and confirm with me before creating. Give each branch an_index.md. - Learning state. Create
.agents/learned/withjournal.md,conventions.md,examples.md, and askills/folder — seed empty starters. - Inbox + dashboard. Create
Inbox/and aDashboard.mdmap-of-content that links the branches and explains the workflow in a line or two. - Commit the scaffold, then point me at
/obsidian-knowledge:helpand suggest dropping a first source intoInbox/.
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 · 48 lines · 19 tokens per session scan A e7c581dfbb31
setup is a command published in the GitHub repository Michael-OvO/obsidian-knowledge-agent (204 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 672 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
install
Guided setup for a new Cowork workspace. Interviews you (about 5 minutes) and generates a full, pre-configured cowork-os workspace (folders, copy, project instructions, and recurring routines).
process-inbox
Process the inbox. Read everything the user dropped in (notes, links, a deck, a messy folder) and route each fact to the most specific workspace file, separating facts from assumptions and open questions, without inventing anything.
plan
Create a phased implementation plan before writing any code.
megacave
Activate megacave mode (caveman in Classical Chinese).
help
Quick reference for all Attune commands.
fire-todos
Capture, list, and manage todos during work sessions.