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-prep-1on1.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-prep-1on1)<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-prep-1on1"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-prep-1on1/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-prep-1on1"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-prep-1on1.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.00788 |
| Opus 5 | $0.00012 | $0.00394 |
| Sonnet 5 | $0.00005 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
om-prep-1on1 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 9d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prep for 1:1
Prepare for an upcoming 1:1 by gathering everything relevant about the person and current work context.
Usage
/om-prep-1on1 <person>
Example: /om-prep-1on1 Scott Detweiler
Workflow
-
Load person context — read
org/people/$ARGUMENTS.mdfor role, relationship, key moments, and any standing dynamics -
Load recent 1:1 history — check
work/1-1/for prior notes with this person; surface:- Unresolved action items from last meeting
- Topics that recurred across sessions
- Anything flagged in "What to Watch"
2b. Carry-forward check — open the person's last THREE 1:1 notes and diff their Action Items: any unchecked item appearing (same or near-same wording) in two or more consecutive notes is a chronic loop, not just an open one. List these separately with their first-seen date — "carried 3× since " is the prep signal a single note can never show. (The hooks' open-loops flag only reads the latest note; this step is where the chronic pattern surfaces.)
-
Load active work — read
work/Index.mdand relevantwork/active/**/*.mdnotes (recursive — grouped workstreams live inactive/<Topic>/subfolders); identify:- Projects this person is connected to (via wikilinks or shared team)
- Blockers or open questions that need a decision or support
- Work in progress worth giving visibility to
-
Check North Star alignment — read
brain/North Star.md; flag:- Goals drifting or with no active work
- Emerging focus that hasn't been written down yet
-
Surface wins to share — check
perf/Brag Doc.mdand the current quarter's brag note for completed work or milestones since the last 1:1 with this person -
Check open tasks — run
obsidian tasks daily todo; flag any stalled or overdue items -
Present the prep brief:
- Who — one-line reminder: role, relationship, standing dynamics
- Since Last Time — unresolved action items, open "What to Watch" signals
- Chronic Loops — items carried across 2+ consecutive 1:1s (from step 2b), oldest first; each one is either blocked (raise it), obsolete (kill it), or under-prioritized (say so)
- Wins to Share — completed work and milestones worth mentioning, with enough context to explain impact
- Things to Raise — blockers needing a decision, projects needing visibility, North Star drift
- Questions to Ask — based on vault gaps or unclear priorities
- Suggested Agenda — rough order if there are 3+ items: wins → updates → asks → questions
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.
- 9d ago First seen · 61 lines · 24 tokens per session scan A 434b8f82eb2a
om-prep-1on1 is a command published in the GitHub repository breferrari/obsidian-mind (4,619 stars, last pushed 6d ago), licensed MIT. It adds 24 tokens to every session and 788 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
kb-ingest
Ingest external material into Sources/ inside the bound project KB, then update registry, index, and daily note as needed.
kb-promote
Promote durable content from Daily or source notes into canonical Knowledge, Experiments, Results, Results/Reports, or Writing notes.
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.
onboard
An interview-based setup command for an LLM Wiki, a notes system designed for use with language models. It asks about your wiki, files, working mode, and personal context, then fills in the setup details.