session-search

session-search is a skill for Claude Code from glebis/claude-skills. It costs 50 tokens per session (501 once invoked), scanned A, original, MIT.

A search tool for finding past Claude Code conversation transcripts using natural-language queries. It can match related words and concepts, not just exact terms.

In plain words
What is it for?
Use it to find earlier sessions about a topic, problem, project, or task.
Why use it?
It removes the need to remember which conversation contained a decision, debugging session, research task, or piece of work.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the session-search plugin — 1 skill shipped together

Good fit Use it to find earlier sessions about a topic, problem, project, or task.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/glebis/claude-skills/session-search
Install

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.

Any agent
npx skills add glebis/claude-skills --skill session-search
Clone the repo
git clone --depth 1 https://github.com/glebis/claude-skills

Made for: Claude Code.

Or install session-search, the plugin that ships this one along with the rest of its 1 skill.

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.

agentmods badge for session-search

README.md
[![agentmods](https://agentmods.dev/badge/skills/glebis/claude-skills/session-search/github.svg)](https://agentmods.dev/skills/glebis/claude-skills/session-search)
Your own site
<a href="https://agentmods.dev/skills/glebis/claude-skills/session-search"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/session-search/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.

agentmods 80×15 button for session-search

Your own site · 80×15
<a href="https://agentmods.dev/skills/glebis/claude-skills/session-search"><img src="https://agentmods.dev/badge/skills/glebis/claude-skills/session-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 501 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00050 $0.00501
Opus 5 $0.00025 $0.00251
Sonnet 5 $0.00010 $0.00100
Haiku 4.5 $0.00005 $0.00050

Measured 7d ago against content hash 079937c864dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

session-search 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 7d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/search.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

session-search/SKILL.md · 61 lines

What it actually says

Search Claude Code session transcripts by combining keyword pre-filtering with semantic evaluation. Finds previous sessions about specific topics, debugging conversations, research tasks, or any past work.

Workflow

Step 1: Run the search script

Execute scripts/search.py with the user's query:

python3 scripts/search.py "<query>" [max_results] [max_age_days]
  • query (required): Natural language search query
  • max_results (optional, default 10): Maximum results to return
  • max_age_days (optional, default 90): How far back to search

The script performs keyword pre-filtering across all sessions, then extracts meaningful excerpts from top candidates. Output contains a SESSIONS_DATA JSON block.

Step 2: Evaluate results semantically

After receiving the script output, evaluate each session's relevance to the query. Consider:

  • Synonym matching: "bug" matches "error", "issue", "problem", "fix"
  • Related concepts: "debugging" matches sessions with test failures or error messages
  • Tool patterns: "refactoring" matches Edit-heavy sessions
  • Domain context: "obsidian" matches vault-related work

Assign a relevance score (0-10) to each session based on excerpt content and query intent.

Step 3: Present results

Display the top results (up to max_results) sorted by relevance, formatted as:

### [Relevance: N/10] Project — Date
Summary of what the session was about (1-2 sentences based on excerpts)
`claude --resume <session-id>`

If no relevant results are found, report that and suggest alternative queries.

Session Storage

Sessions are stored as JSONL files in ~/.claude/projects/. Each file contains events with user/assistant messages and tool calls. The search script handles file discovery and text extraction automatically.

Customization

To search older sessions or get more results:

/session-search "query" 20 180

(20 results, 180 days lookback)

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

  1. 7d ago First seen · 61 lines · 50 tokens per session scan A 079937c864dd

Subscribe to this mod's changes

session-search is a skill published in the GitHub repository glebis/claude-skills (374 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 501 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-09-03.