obsidian-mind: Command for Claude Code

.claude/commands/om-weekly.md

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

A weekly review command for an Obsidian vault, which is a folder of linked notes. It analyzes recent work, goals, patterns, missed accomplishments, and next priorities.

In plain words
What is it for?
It is for reviewing recent commits and note changes, comparing activity with a North Star plan, finding drift and neglected goals, and preparing forward priorities.
Why use it?
It reveals whether the week's activity matched the stated direction and surfaces useful work or emerging themes that were not recorded.

Command for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: mentions subagents.

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,605 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-weekly.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-weekly

README.md
[![agentmods](https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-weekly.svg)](https://agentmods.dev/commands/breferrari/obsidian-mind/om-weekly)
Your own site
<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-weekly"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-weekly.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 974 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.00024 $0.00974
Opus 5 $0.00012 $0.00487
Sonnet 5 $0.00005 $0.00195
Haiku 4.5 $0.00002 $0.00097

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

Security

Grade A, and why

om-weekly 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 7d 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-weekly.md · 92 lines

How it starts

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

Cross-session synthesis of the past week. Bridges daily standup (lightweight) and quarterly review brief (comprehensive). This is ANALYSIS, not verification — find patterns, surface drift, detect uncaptured work.

Subagent

  • brag-spotter — run with weekly scope to find uncaptured wins and competency gaps

Workflow

1. Gather Week's Activity

Automated — no user input needed:

  • git log --since="7 days ago" --oneline --no-merges — all vault changes
  • List all notes modified in the past 7 days (git + filesystem)
  • Read any work/1-1/*.md notes from this week
  • Check work/active/ for status changes
  • Check work/incidents/ for new or updated incidents
  • Read today's daily note if it exists: obsidian daily:read

2. North Star Alignment

Read brain/North Star.md and compare actual activity against stated focus:

  • Aligned work: which Current Focus items got attention this week?
  • Drift: work that doesn't map to any stated goal (not necessarily bad — flag it)
  • Silent goals: focus items with zero commits, zero note updates, zero mentions
  • Emerging themes: work patterns suggesting a focus shift that hasn't been written down yet

3. Cross-Day Patterns

Look across the week's notes for:

  • Recurring themes (same topic in multiple notes or days)
  • Multiple incidents or issues touching the same system
  • Topics appearing in BOTH work notes and 1:1s (these are signals)
  • Context that evolved across sessions (decisions that shifted, understanding that deepened)

4. Uncaptured Win Detection

Run the brag-spotter subagent with its standard (quarterly) scope, then filter its findings down to wins that clearly occurred in the past 7 days.

Additionally check:

  • Were completed items logged in perf/Brag Doc.md or the current quarter's brag note?
  • Any 1:1 feedback or kudos not captured?
  • Incident contributions not bragged about?

5. Competency Signal Mapping

For each competency in perf/competencies/:

  • Was it exercised this week? (check work note links, incident roles, 1:1 topics)
  • If yes, is the competency explicitly linked from the evidence note?

Read the full file on GitHub · 92 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. 7d ago First seen · 92 lines · 24 tokens per session scan A aa66ecd9083a

Subscribe to this mod's changes

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