session-search
Find Claude Code sessions tracked by the Agent Monitor by project (cwd), model, status, or date, then rank the matches by cost or recency. Pulls the session list and the distinct cwd / facet values so filters use real values rather than guesses. Use when locating a session — "find my EstateWise sessions", "which Opus runs errored this week", "most expensive sessions in /repo".
Profile →npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-search --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Session Search 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`) - **model** — `opus`, `sonnet`, `haiku`, or a full model id substring - **status** — `active`, `working`, `completed`, `error` - **date** — `today`, `this week`, or an ISO date / range matched against `started_at` - **ranking** — `by 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 filt
- Input
- Data Sources
- Report Sections
- 1. Resolve filters
- 2. Pull candidates
- 3. Rank
- 4. Matches
- 5. Summary
- Output
What does the session-search skill do?
Find Claude Code sessions tracked by the Agent Monitor by project (cwd), model, status, or date, then rank the matches by cost or recency. Pulls the session list and the distinct cwd / facet values so filters use real values rather than guesses. Use when locating a session — "find my EstateWise sessions", "which Opus runs errored this week", "most expensive sessions in /repo".
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill session-search --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.