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-project-archive.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-project-archive)<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-project-archive"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-project-archive/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-project-archive"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-project-archive.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.00430 |
| Opus 5 | $0.00000 | $0.00215 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
om-project-archive 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.
What it actually says
Project Archive
Move a completed project from work/active/ to work/archive/YYYY/ and update all indexes.
Usage
/om-project-archive <project name>
Workflow
1. Find the Note
Search work/active/ for the project name. Confirm with the user before proceeding.
2. Update Frontmatter
- Set
status: completed - Verify
quarterproperty is set correctly - Verify
descriptionreflects the final state
3. Move the File
git mv "work/active/<Note>.md" "work/archive/YYYY/"
Use the year from the note's date field.
Clustered workstreams: when the project lives in a topic folder (work/active/<Topic>/ — the grouping convention for >1-note workstreams), move the WHOLE folder and keep the grouping:
git mv "work/active/<Topic>" "work/archive/YYYY/<Topic>"
Every note inside keeps its cluster context, and wikilinks resolve by basename so nothing breaks.
4. Update Indexes
work/Index.md: Move from Active Projects to the appropriate Completed quarter sectionbrain/North Star.md: Mark as completed in Current Focus if listed thereperf/Brag Doc.md: Verify the project is captured in the relevant quarter's highlightsbrain/Memories.md: Update Recent Context if the project is mentioned as "in progress"
5. Verify
- Run a quick check that no wikilinks are broken (Obsidian resolves by name, so moves shouldn't break links)
- Confirm the Work Dashboard Base shows the note in "Completed" view, not "Active Work"
Important
- Always use
git mv— never copy+delete - Don't archive without user confirmation
- If the project has sub-notes (like incidents have RCA + deep dive), ask if those should move too
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 · 56 lines · 0 tokens per session scan A 8f0b082db4ec
om-project-archive 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 430 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-list
List recent sessions from the project ledger and offer to view one.
kamma
Plans, implements, reviews, and finalizes a thread in a single run without requiring prior setup.
pm-autoplan
Orchestre les trois angles de revue (stratégie, utilisateur, faisabilité) en parallèle, puis synthétise leurs pages de stress-test dans output/.
pm-epic-01-happy
Un PRD complet est disponible dans output/ : il contient des exigences P0/P1 avec des critères d'acceptation et une section ## Métriques de succès. Le pm-decomposer crée un epic avec ## Success Criteria et des issues enfants P0/P1 avec critères d'acceptation. Les issues sont liées à l'epic.
pm-review-user-01-happy
Un PRD est disponible dans output/. Le wiki contient des pages persona- et interview- avec des verbatims. Le pm-user-advocate vérifie l'alignement du PRD avec les personas, identifie les personas non servis, cite les verbatims contradictoires, et évalue le niveau de confiance de chaque claim. Une page type…
pm-epic
Décompose un PRD en epic + issues enfants dans beads (délègue au pm-decomposer). Triggers — décomposer un PRD en tickets, transformer une spec en epic beads, créer les issues actionnables d'une feature.