Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add lee-fuhr/claude-session-index --skill session-indexgit clone --depth 1 https://github.com/lee-fuhr/claude-session-indexWrote 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/skills/lee-fuhr/claude-session-index/session-index)<a href="https://agentmods.dev/skills/lee-fuhr/claude-session-index/session-index"><img src="https://agentmods.dev/badge/skills/lee-fuhr/claude-session-index/session-index/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/skills/lee-fuhr/claude-session-index/session-index"><img src="https://agentmods.dev/badge/skills/lee-fuhr/claude-session-index/session-index.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.00033 | $0.00781 |
| Opus 5.5 | $0.00013 | $0.00312 |
| Sonnet 5.5 | $0.00007 | $0.00156 |
| Haiku 4.5 | $0.00003 | $0.00078 |
Grade A, and why
session-index 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session index skill
You have access to a session index — a SQLite database with FTS5 full-text search across all Claude Code sessions. Use it whenever the user asks about past sessions, previous conversations, or wants to know what they've tried before.
The user's interface is this conversation. They ask naturally ("Didn't we discuss browser control recently?"), you translate to CLI commands, and present results conversationally. They should never need to know the CLI syntax.
How to handle session queries
1. Extract keywords from the question
The user says: "Didn't we discuss browser control recently?"
You search: sessions "browser control"
The user says: "What approaches have I tried for form automation?"
You search: sessions "form automation"
The user says: "How much time did I spend on Acme this week?"
You run: sessions analytics --client "Acme" --week
2. Run the right command via Bash
Search — find sessions by topic:
sessions "relevant keywords"
sessions "relevant keywords" --context # includes conversation excerpts
Context — read the actual conversation from a session:
sessions context <session_id> "search term" # exchanges matching a term
sessions context <session_id> # all exchanges
Analytics — effort, time, tool usage:
sessions analytics # overall
sessions analytics --client "Acme" # per client
sessions analytics --week # this week
sessions analytics --month # this month
Filter — find sessions by metadata:
sessions find --client "Acme" # by client
sessions find --tool Task --week # by tool + date
sessions find --project myapp # by project
sessions recent 20 # last N sessions
3. For synthesis ("what worked?", "what have I tried?")
This is the most valuable capability. When the user asks a question that spans multiple sessions:
- Search:
sessions "topic" -n 10 - For the top 3-5 results, extract context:
sessions context <id> "topic" -n 3 - Spawn a Task with
model="haiku"to synthesize:- What approaches were tried?
- What worked / what failed?
- Recurring patterns?
- Current state?
- Present the synthesis conversationally with
claude --resume <id>links for each source session
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.
- 1mo ago First seen · 102 lines · 33 tokens per session scan A 61d8919c53ce
session-index is a skill published in the GitHub repository lee-fuhr/claude-session-index (31 stars, last pushed 7mo ago), licensed MIT. It adds 33 tokens to every session and 781 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.
mnemon
Persistent memory for MiniMax Code. Recall durable context, store important facts and decisions, and link related memories with the mnemon CLI.
mnemon
Persistent memory CLI for Hermes Agent. Store facts, recall past knowledge, link related memories, manage lifecycle.
durable-session-state
Persist plans, scope decisions, evidence, and reviewer/critic verdicts to durable files during long or multi-phase tasks so work survives context compaction, session resumes, and handoffs. Use for swarm-mode tasks, before context grows large, when recording approval gates, and when resuming after compaction or a…
brain-ingest
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.