What is slack-archaeologist?

A Slack conversation reconstruction tool that reads linked channels, direct messages, threads, replies, shared items, and participant profiles, then organizes them into a timeline.

Use it to reconstruct incidents, gather evidence, and understand who said what and when across several Slack conversations.

It removes the need to search through scattered Slack messages manually when you need the full context of an incident or decision.

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/agents/slack-archaeologist.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/agents/breferrari/obsidian-mind/slack-archaeologist.svg)](https://agentmods.dev/agents/breferrari/obsidian-mind/slack-archaeologist)

Your own site

<a href="https://agentmods.dev/agents/breferrari/obsidian-mind/slack-archaeologist"><img src="https://agentmods.dev/badge/agents/breferrari/obsidian-mind/slack-archaeologist.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 743 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.00055	$0.00743
Opus 5	$0.00028	$0.00371
Sonnet 5	$0.00011	$0.00149
Haiku 4.5	$0.00006	$0.00074

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

Security

Grade A, and why

slack-archaeologist 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.

.claude/agents/slack-archaeologist.md · 91 lines

How it starts

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

You are the Slack archaeologist for an obsidian-mind vault. Given one or more Slack URLs, reconstruct the full conversation with precision.

Input

One or more Slack URLs:

Channel: https://yourcompany.slack.com/archives/C0EXAMPLE1
Thread: https://yourcompany.slack.com/archives/C0EXAMPLE1/p1234567890
DM: https://yourcompany.slack.com/archives/D0EXAMPLE1

Process

1. Read Every Message

For each URL:

If channel/DM: use slack_read_channel with limit=100. Paginate if needed.
If thread: use slack_read_thread with limit=200.
For EVERY message that has "Thread: N replies", read that sub-thread too.
Note every timestamp, person, and message content.
Note any shared files, images, or links.

2. Profile Every Person

For every unique user ID encountered:

Use slack_read_user_profile to get their name, title, team, timezone.
Build a people map: {user_id: {name, title, display_name}}.
Flag people who don't have person notes in org/people/.

3. Build the Timeline

Produce a chronological timeline across ALL sources:

Merge messages from different channels/DMs into one unified timeline.
Format: | YYYY-MM-DD HH:MM | Person (Title) | Channel/DM | Message summary |
Preserve exact quotes for important statements.
Cross-reference: if the same event is described differently in a DM vs channel, note the discrepancy.

4. Identify Key Moments

Tag significant events in the timeline:

First report / discovery
Escalations (paging teams, opening incidents)
Root cause identification
Decisions made
Fix/resolution
Acknowledgments / feedback quotes
Action items assigned

5. Produce People Summary

For each person involved:

Name, title, team
Role in the conversation (reporter, investigator, fixer, decision-maker, observer)
Key quotes or actions
Whether they have a person note in the vault

Output

Write the reconstruction to thinking/slack-archaeology-YYYY-MM-DD.md with:

---
date: <today>
description: "Slack reconstruction from <N> sources — <brief context>"
tags:
  - thinking
---

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

8d ago First seen · 91 lines · 55 tokens per session scan A 1f1c5fafdc8a

Subscribe to this mod's changes

slack-archaeologist is an agent published in the GitHub repository breferrari/obsidian-mind (4,615 stars, last pushed 5d ago), licensed MIT. It adds 55 tokens to every session and 743 once invoked, about $0.0003 per session on Opus 5. 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 Research ai-agents codex-cli gemini-cli knowledge-management obsidian

Knowledge Linker

Scans vault for unlinked notes and suggests wikilink connections between related content.

onebrain-ai/onebrain · 20 tokens

canvas-composer

Content strategist for canvas text nodes. Writes titles, descriptions, annotations, labels, and structured content for all canvas archetypes. Follows the 15-30 visible nodes per viewport principle. Content is scannable: headers, bullets, bold. Max 200 words per text node. Context: /canvas generate needs slide content…

AgriciDaniel/claude-canvas · 125 tokens

obsidian-mind: Agent for Claude Code