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-incident-capture.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-incident-capture)<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-incident-capture"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-incident-capture/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-incident-capture"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-incident-capture.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.00000 | $0.01065 |
| Opus 5 | $0.00000 | $0.00532 |
| Sonnet 5 | $0.00000 | $0.00213 |
| Haiku 4.5 | $0.00000 | $0.00106 |
Grade A, and why
om-incident-capture 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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Incident Capture
Capture an incident from Slack channels, DMs, and threads into structured vault notes. Produces a complete incident work note with timeline, people, analysis, and brag doc entry.
Usage
/om-incident-capture <slack-urls>
Provide one or more Slack URLs: incident channels, DM conversations, threads. The more context, the better.
Subagents
This command orchestrates two subagents for heavy lifting:
slack-archaeologist— reads all Slack sources, builds unified timeline with attributionpeople-profiler— bulk creates/updates person notes for everyone involved
Launch both in parallel when starting the capture.
Workflow
1. Gather Raw Data
For each Slack URL provided:
- Read the full channel/DM/thread using
slack_read_channelorslack_read_thread - Read ALL sub-threads within the channel (check for "Thread: N replies" indicators)
- Note every timestamp, person, and message — nothing is too small
- Download and examine any shared images or files
2. Identify People
For every person who posted or was mentioned:
- Fetch their Slack profile (
slack_read_user_profile) - Check if they have a person note in
org/people/ - Note their role, team, and title
- Track who did what (reported, investigated, fixed, confirmed, etc.)
3. Build the Timeline
Reconstruct a detailed timeline from all sources:
- Every message with exact timestamp (CET)
- Attribution: who said/did what
- Cross-reference between channels (same person posting in incident channel + DMs)
- Key moments: first report, incident declared, root cause identified, fix created, fix merged, resolution confirmed
4. Create the Work Note
Create work/incidents/<Incident Name>.md with:
---
date: "YYYY-MM-DD"
quarter: QN-YYYY
description: "~150 chars"
project: <relevant project>
status: active
ticket: TICKET-XXXX
severity: high/medium/low
role: <your role>
tags:
- work-note
- incident
---
Sections:
- Context — what happened, what triggered it, who was involved
- Root Cause — technical explanation
- Resolution — fix PR(s), what changed
- Timeline — full detailed table with timestamps
- Impact — users affected, business impact
- Involved Personnel — with wikilinks to person notes
- Notes — key actions by the user, analysis
- Analysis — what this means strategically (pattern, visibility, competencies)
- Related — wikilinks to all related notes, competencies
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.
- 10d ago First seen · 120 lines · 0 tokens per session scan A 306261f95c2e
om-incident-capture is a command published in the GitHub repository breferrari/obsidian-mind (4,620 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,065 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.
Other commands, from other repositories
wiki-lint
Run a health check on the wiki. Invoke with /wiki-lint or "lint the wiki".
okf
A command that exports a private knowledge wiki into an OKF-compatible bundle. OKF is a format for packaging knowledge, with a separate guarded mode for preparing material to share externally.
pdf-to-wiki
A workflow for sending a large PDF from Google Drive to NotebookLM, Google's document-analysis tool, and saving the resulting notes as Obsidian markdown files. It passes the file link rather than reading the PDF directly.
ingest
Compile new sources from raw/ into the wiki.
ingest
Ingest a source (URL/file/text) into Raw Sources + compile 1015 Wiki pages, with mandatory user-purpose gate and mothership cross-linking.
lint
Run comprehensive wiki health check — orphans, broken links, contradictions, stale pages, index sync, MOC coverage, v2/v4/v5 frontmatter coverage, Core Context freshness, and cross-vault link integrity (mainVaultRelated/mainVaultCmds).