A checklist for reviewing a work session before it ends, including changed files, notes, indexes, decisions, and possible improvements.

Use it at the end of a session to review modified notes, check their metadata and links, verify indexes, and identify uncaptured lessons.

It helps ensure the session's records are complete, consistent, correctly filed, and easy to find later.

How breferrari/obsidian-mind configures Claude Code

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,615 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-wrap-up.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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-wrap-up/github.svg)](https://agentmods.dev/commands/breferrari/obsidian-mind/om-wrap-up)

Your own site

<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-wrap-up"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-wrap-up/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-wrap-up"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-wrap-up.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 837 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00837
Opus 5	$0.00000	$0.00418
Sonnet 5	$0.00000	$0.00167
Haiku 4.5	$0.00000	$0.00084

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

Security

Grade A, and why

om-wrap-up 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.

.claude/commands/om-wrap-up.md · 89 lines

How it starts

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

Wrap Up

Full session review before ending. Review context, ways of working, files modified, consistency, and suggest improvements.

Usage

/om-wrap-up

Triggered when the user says "wrap up", "let's wrap", "wrapping up", or similar. Claude should invoke this automatically.

Subagent

brag-spotter — run at the end to find uncaptured wins and competency gaps from the session

Workflow

1. Review What Was Done

Scan the conversation for:

Notes created or modified (list them all with paths)
People notes created or updated
Indexes updated
Brag doc entries added
Brain notes updated (Patterns, Gotchas, Key Decisions, Memories)

2. Verify Note Quality

For each note created or modified this session:

Frontmatter complete? (date, quarter, description, tags, type-specific fields)
At least one wikilink to another note?
In the correct folder? (work/active/ vs work/archive/ vs work/incidents/ etc.)
Description accurate and ~150 chars?
Status field correct?

3. Check Index Consistency

work/Index.md — are new notes linked? Are completed projects in the right section?
brain/Memories.md — does Recent Context reflect what happened this session?
Auto-memory index — if brain/ notes were added or their descriptions changed, REGENERATE the index instead of hand-editing it: node --experimental-strip-types .claude/scripts/generate-memory-index.ts > <your ~/.claude/projects/<slug>/memory/MEMORY.md path>. MEMORY.md is a derived view (pointers only); hand edits get overwritten by design.
org/People & Context.md — any new people or relationship changes to capture?
perf/Brag Doc.md — any wins or achievements from this session?
Home.md — are embedded Bases still valid?

4. Check for Orphans

Any new notes not linked from at least one other note?
Any new people not added to People & Context?
Any thinking notes that should be promoted or deleted?

5. Archive Check

Are there notes in work/active/ that should be moved to work/archive/YYYY/?
Any status fields still active that should be completed?

Read the full file on GitHub · 89 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.

9d ago First seen · 89 lines · 0 tokens per session scan A 9c9957f11c7b

Subscribe to this mod's changes

om-wrap-up is a command published in the GitHub repository breferrari/obsidian-mind (4,615 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 tokens. 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.

Claude Code ai-agents codex-cli gemini-cli knowledge-management obsidian

obsidian-mind: Command for Claude Code