obsidian-mind: Command for Claude Code

.claude/commands/om-meeting.md

om-meeting is a command for Claude Code from breferrari/obsidian-mind. It costs 29 tokens per session (774 once invoked), scanned A, original, MIT.

A meeting-preparation command that builds a briefing around a topic by searching an Obsidian-style work vault, a folder of linked notes. It gathers current status, related work, past decisions, unresolved tasks, blockers, and possible discussion points.

In plain words
What is it for?
Use it to prepare for meetings about projects, processes, decisions, or technical topics.
Why use it?
It removes the need to search through scattered notes before a meeting and helps surface issues that may otherwise be missed.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is breferrari/obsidian-mind's own configuration. It tells Claude Code how to work on obsidian-mind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything obsidian-mind configures →

Part of the obsidian plugin — 8 skills, 20 commands, 10 agents, 5 hooks, 1 MCP server shipped together

About the project

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.

breferrari/obsidian-mind · 4,620 stars · on GitHub

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/breferrari/obsidian-mind/main/.claude/commands/om-meeting.md
Clone the repo
git clone --depth 1 https://github.com/breferrari/obsidian-mind

Made for: Claude Code.

Or install obsidian, the plugin that ships this one along with the rest of its 8 skills, 20 commands, 10 agents, 5 hooks, 1 MCP server.

Wrote 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.

agentmods badge for om-meeting

README.md
[![agentmods](https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-meeting/github.svg)](https://agentmods.dev/commands/breferrari/obsidian-mind/om-meeting)
Your own site
<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-meeting"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-meeting/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.

agentmods 80×15 button for om-meeting

Your own site · 80×15
<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-meeting"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-meeting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 774 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.00774
Opus 5 $0.00015 $0.00387
Sonnet 5 $0.00006 $0.00155
Haiku 4.5 $0.00003 $0.00077

Measured 10d ago against content hash 94a2d7c6b81a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

om-meeting 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 10d 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.

.claude/commands/om-meeting.md · 80 lines

How it starts

The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Meeting Prep

Deep briefing on a subject before a meeting. Leads with the topic, not the people. Surfaces what's unresolved and brainstorms considerations, risks, and angles that may not have been raised yet.

Usage

/om-meeting <topic>

Examples:

  • /om-meeting Janus Project
  • /om-meeting Legal sign-off workflow
  • /om-meeting Qwen font exploration
  • /om-meeting ComfyUI model server access

Workflow

  1. Search the vault — run qmd query "$ARGUMENTS" and qmd vsearch "$ARGUMENTS" to find everything related to the topic, including semantically related content

  2. Load all related notes — read every relevant result: work notes, decisions, incidents, person notes, team notes. A meeting about one topic often touches adjacent projects and prior decisions

  3. Build the subject picture — synthesize what the vault knows:

    • Current status and recent changes
    • How this topic connects to other active work
    • Prior decisions that affect this topic
    • Outstanding items directly tied to this subject
  4. Surface open items — collect all unresolved threads related to the topic:

    • Open checkboxes (- [ ]) from related notes
    • Documented blockers
    • Questions raised but not answered
    • Status fields with no recent movement
  5. Brainstorm considerations — go beyond what's in the vault; think through:

    • What could go wrong that hasn't been written down yet
    • Dependencies on other teams, people, or systems not yet flagged
    • Decisions that will likely need to be made — and what the options are
    • Edge cases or failure modes worth raising
    • Things that have tripped up similar work before (check brain/Gotchas.md)
    • Stakeholders who aren't in the room but whose work this affects
  6. Note relevant people — list who's involved and their role relative to this topic only (not relationship history or 1:1 context — that's /om-prep-1on1)

  7. Present the briefing:

    Current State

    Concise synthesis of where things stand on this topic right now.

Read the full file on GitHub · 80 lines

Changes

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.

  1. 10d ago First seen · 80 lines · 29 tokens per session scan A 94a2d7c6b81a

Subscribe to this mod's changes

om-meeting is a command published in the GitHub repository breferrari/obsidian-mind (4,620 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 774 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.