Session Search

CommunityPopular

hoangsonww

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".

Overview

Publisher	hoangsonww
Repository	`Claude-Code-Agent-Monitor`
Skill name	`session-search`
Stars	1.1K
Forks	260
Bundled files	1
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by hoangsonww on GitHub. Read the source before you install it.

Installation

Install the Session Search AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-search
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-search

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor.git /tmp/Claude-Code-Agent-Monitor
mkdir -p .claude/skills
cp -r /tmp/Claude-Code-Agent-Monitor/plugins/ccam-sessions/skills/session-search .claude/skills/session-search

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Session Search in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Session Search on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Session Search is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Output

Markdown table: # | id (short) | status | model | cwd (basename) | started_at | cost. Currency as USD to 4 decimal places; token / count fields with thousands separators. If a filter resolved to zero rows, say so and show the closest available values (e.g. the cwds that do exist) rather than fabricating results. If the dashboard is unreachable, tell the user to start it with npm start from the repo root.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB

Frequently asked questions

What does the Session Search AI skill do?

Why use Session Search on TypingMind?

Because you install it once and use it with any model. Session Search is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Session Search in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/hoangsonww/Claude-Code-Agent-Monitor/tree/master/plugins/ccam-sessions/skills/session-search. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Session Search?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Session Search?

As many as you like. As long as a model supports skills, you can use Session Search with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Session Search AI skill free?

Yes. It is published on GitHub by hoangsonww under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Stats

JuliusBrussee

CommunityPopular

Show recorded output and cache-read token usage and mode attribution for the current Claude Code session, or locate the host's native usage report. Trigger: /caveman-stats.

Ci Metrics

Query PyTorch CI, GitHub Actions, HUD, Grafana, and infrastructure metrics. Use when users ask about CI duration, job failures, queue times, workflow trends, runner health, dashboard data, or PyTorch…

Notcrawl

Notion archive: search, sync freshness, pages/databases, Markdown exports, SQL counts, and Notcrawl repo work.

Openclaw Test Heap Leaks

openclaw

OrganizationPopular

Investigate OpenClaw pnpm test memory growth, Vitest OOMs, RSS spikes, and heap snapshot deltas.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Session Search

Input

Data Sources

Report Sections

1. Resolve filters

2. Pull candidates

3. Rank

4. Matches

5. Summary

Output

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now