session-search

session-search is a skill for Claude Code, Codex from hoangsonww/Claude-Code-Agent-Monitor. It costs 86 tokens per session (706 once invoked), scanned A, original, MIT.

A search tool for locating Claude Code sessions by project folder, model, status, or date. It can rank matching sessions by cost or by how recently they ran.

In plain words
What is it for?
Use it to find sessions for a project, model, time period, or status, then sort the results by spending or recency.
Why use it?
It removes the need to scan a long session list when you need to find one particular run or compare recent work.

Skill for Claude CodeCodex

Written for Claude Code and Codex: $ARGUMENTS substitution, but also agents/openai.yaml present. Also seen: mentions Claude Code.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/.../repo.

Part of the ccam-sessions plugin — 5 skills, 3 commands, 1 agent shipped together

Good fit Use it to find sessions for a project, model, time period, or status, then sort the results by spending or recency.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor
Claude Code
/plugin install ccam-sessions

Made for: Claude Code, Codex.

Or install ccam-sessions, the plugin that ships this one along with the rest of its 5 skills, 3 commands, 1 agent.

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/hoangsonww/claude-code-agent-monitor/session-search/github.svg)](https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/session-search)
Your own site
<a href="https://agentmods.dev/skills/hoangsonww/claude-code-agent-monitor/session-search"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/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/hoangsonww/claude-code-agent-monitor/session-search"><img src="https://agentmods.dev/badge/skills/hoangsonww/claude-code-agent-monitor/session-search.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 706 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00086 $0.00706
Opus 5 $0.00043 $0.00353
Sonnet 5 $0.00017 $0.00141
Haiku 4.5 $0.00009 $0.00071

Measured 9d ago against content hash b0841a96c7f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 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.

plugins/ccam-sessions/skills/session-search/SKILL.md · 66 lines

How it starts

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

Locate Claude Code sessions in the Agent Monitor by project, model, status, or date.

Input

The user provides: $ARGUMENTS

A free-form query naming any combination of:

  • project / cwd — a working-directory path or basename (e.g. EstateWise, /Users/.../repo)
  • modelopus, sonnet, haiku, or a full model id substring
  • statusactive, working, completed, error
  • datetoday, this week, or an ISO date / range matched against started_at
  • rankingby cost (default when cost is mentioned) or recent (default otherwise)

If the query is empty, return the most recent sessions ranked by recency.

Data Sources

Endpoint Returns
GET /api/sessions?limit=N session list: id, status, model, cwd, started_at, ended_at, cost, metadata (thinking_blocks, turn_count, total_turn_duration_ms, usage_extras)
GET /api/run/cwds the distinct working directories that have sessions — use to resolve a fuzzy project name to exact cwd values
GET /api/events/facets distinct facet values (event types, tool names, models, statuses) for validating filters

Report Sections

1. Resolve filters

Fetch /api/run/cwds and /api/events/facets to map the user's loose terms to real values: pick the cwd(s) whose path contains the project term, confirm the model substring exists, and validate the status against known statuses. State which concrete filters you settled on.

2. Pull candidates

GET /api/sessions?limit=200 (raise the limit if the date window is wide). Filter in-memory by cwd, model (substring, case-insensitive), status, and started_at date window.

3. Rank

Sort by cost descending when the user asked "by cost"; otherwise by started_at descending (most recent first). Keep the top 20 unless the user asked for more.

4. Matches

One row per session.

5. Summary

Count of matches, summed cost across matches, and the model / status distribution.

Read the full file on GitHub · 66 lines

Files

What ships with it

1 file 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. 9d ago First seen · 66 lines · 86 tokens per session scan A b0841a96c7f7

Subscribe to this mod's changes

session-search is a skill published in the GitHub repository hoangsonww/Claude-Code-Agent-Monitor (991 stars, last pushed 4d ago), licensed MIT. It adds 86 tokens to every session and 706 once invoked, about $0.0004 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.