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-slack-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-slack-scan)<a href="https://agentmods.dev/commands/breferrari/obsidian-mind/om-slack-scan"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-slack-scan/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-slack-scan"><img src="https://agentmods.dev/badge/commands/breferrari/obsidian-mind/om-slack-scan.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.00475 |
| Opus 5 | $0.00000 | $0.00237 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
om-slack-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- slack-scan — 89% identical, 8 lines differ
What it actually says
Slack Deep Scan
Deep scan Slack channels and DMs for evidence involving a specific person or project. Extracts every touchpoint with timestamps for review evidence or project documentation.
Usage
/om-slack-scan <target> [channels...] [date-range]
Examples:
/om-slack-scan "Jane Doe" C0EXAMPLE1 C0EXAMPLE2 "after:2026-03-16"/om-slack-scan "project:example" C0EXAMPLE1 C0EXAMPLE2 C0EXAMPLE3 C0EXAMPLE4
Workflow
-
Read each channel fully (paginate with cursor until all messages are fetched):
mcp slack_read_channel channel_id=<id> limit=100 -
Search for the person across public+private channels:
mcp slack_search_public_and_private query="from:<@USER_ID> after:<date>" mcp slack_search_public_and_private query="<Name> after:<date> -from:<@USER_ID>" -
Check DMs the user points to. Read full history for the relevant period.
-
For each message involving the target, extract:
- Timestamp and channel
- What was said/done
- Context (what prompted it, what followed)
- Whether it's evidence of: technical work, leadership, collaboration, problem-solving, initiative
-
Organize by date with clear headers per day. Separate:
- Project evidence → goes to the relevant work note
- Review/personal context → goes to people notes or review prep notes
- Team dynamics → goes to people notes
-
Flag items that need correction in existing vault notes.
Important
- Be meticulous — timestamps matter for evidence
- Capture exact quotes when they show initiative, leadership, or problem-solving
- Note when the person was tagged by others (shows they're a go-to person)
- Separate project work from review prep from personal conversations
- Don't mix contexts — put data where it belongs in the vault
- Check for threads (slack_read_thread) when a message has replies
- Look for screen recordings, files shared, PRs linked
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 · 52 lines · 0 tokens per session scan A 52a9b7064ebb
om-slack-scan 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 475 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.