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-peer-scan.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-peer-scan)<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-peer-scan"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-peer-scan.svg" alt="Measured on agentmods" 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.00505 |
| Opus 5 | $0.00000 | $0.00253 |
| Sonnet 5 | $0.00000 | $0.00101 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
om-peer-scan 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 8d 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.
What it actually says
Peer PR Deep Scan
Deep scan a peer's GitHub PRs for performance review preparation. Produces a structured analysis saved to perf/evidence/.
Usage
/om-peer-scan <name> <github-username> <repo> [period]
Example: /om-peer-scan "Jane Doe" jdoe example-repo "Jan 2025 - Jun 2025"
Workflow
-
Fetch full PR list (limit 200):
gh pr list --repo <org>/<repo> --author <username> --state all --limit 200 --json number,title,state,createdAt,mergedAt,additions,deletions -
Filter to review period (default: last 6 months). For EACH PR in period, fetch details:
gh pr view <number> --repo <org>/<repo> --json body,reviews,comments,additions,deletions,changedFiles,title,state,createdAt,mergedAt -
Produce structured analysis with these sections:
- PR count by month — table showing velocity trends
- Projects/themes — group PRs by project area with descriptions of what was built
- Quality signals — review comments, change requests, approval patterns, reverts, static analysis findings
- Notable contributions — architectural decisions, complex fixes, test coverage, cross-team impact
- Growth signals — scope expansion over time, leadership evidence
- Full PR table — every PR with number, title, date, additions, deletions, state
-
Save to vault as
perf/evidence/<Name> PRs - <Period>.mdwith frontmatter:--- date: "<today>" description: "<one-line summary of findings>" person: "<Full Name>" cycle: "<e.g. h1-2026>" tags: - perf - evidence ---
Important
- Be thorough — this feeds into performance reviews
- Note PRs that were reverted or closed (quality signal)
- Look for patterns in reviewer feedback (recurring issues = growth area)
- Identify cross-team PRs (collaboration evidence)
- Flag weekend/late-night work patterns if visible
- Map PRs to projects you have context on
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.
- 8d ago First seen · 54 lines · 0 tokens per session scan A 5d930127a62e
om-peer-scan is a command published in the GitHub repository breferrari/obsidian-mind (4,615 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 505 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
session-stop
Stop recording and save this agent session to the project ledger.
sol
Run a one-shot task on the routed Codex model (gpt-5.6-sol by default) and relay its answer.
setup
Configure Vault PKM plugin — set vault path, API keys, and verify setup.
review-code
4-dimension code review for implementation quality.
query-synthesis-01-happy
Le wiki contient plusieurs pages cohérentes sur la notion de dette technique vue d'un angle produit. L'utilisateur demande une synthèse. Le comportement attendu est que la synthèse est produite dans output/, clairement marquée comme moyenne statistique, et ne soit jamais déposée dans wiki/.
resource
Summarize URL(s) and create formatted vault note(s).