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 agentmods add skills/theshadow27/mcp-cli/find-sessionnpx skills add theshadow27/mcp-cli --skill find-sessiongit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/theshadow27/mcp-cli/find-session)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/find-session"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/find-session.svg" alt="Measured on agentmods" 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 | $0.00049 | $0.01885 |
| Opus 5 | $0.00024 | $0.00942 |
| Sonnet 5 | $0.00010 | $0.00377 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
find-session 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 4d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Session Skill
Search through Claude Code session history files (JSONL) to find past conversations by keyword OR by recency, then summarize and rank matches for easy resumption.
When to Use
Trigger when the user:
- Wants to find a past conversation ("find the session where we discussed X")
- Can't remember which window had a specific discussion
- Wants to resume work from a previous session
- Wants to see their most recent sessions ("what were my last N sessions", "what was I working on yesterday")
- Says
/find-session
Two Search Modes
- Keyword search (
search-sessions.ts) — for "find the session about X". See Workflow: Keyword Search below. - Recency listing (
recent-sessions.ts) — for "what were my last N sessions". See Workflow: Recency Listing below.
Pick based on whether the user has a topic in mind or just wants a chronological list.
Workflow: Keyword Search
Step 1: Extract Keywords
From the user's request, identify keywords and/or literal phrases:
- Quoted phrases (
"feature/PROJ-123") — matched as exact substrings (case-insensitive). Use for branch names, ticket IDs with prefixes, error messages, file paths, or any string where the exact form matters. - Unquoted words — tokenized and matched via BM25. Use for general concepts, function names, topics.
- Cast a wider net — the search matches ANY keyword/phrase, so more terms = better ranking (sessions matching more score higher)
Tell the user what keywords you're searching for.
Step 2: Run the Search
.claude/skills/find-session/scripts/search-sessions.ts [keyword] ["literal phrase"] ... [--max 10]
Examples:
# Tokenized keywords (matches "auth", "middleware" independently)
.claude/skills/find-session/scripts/search-sessions.ts auth middleware refactor
# Literal phrase (matches exact substring "feature/fix-auth-middleware")
.claude/skills/find-session/scripts/search-sessions.ts '"feature/fix-auth-middleware"'
# Mixed: literal phrase + tokenized keywords
.claude/skills/find-session/scripts/search-sessions.ts '"PROJ-123"' branch deploy
What ships with it
3 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.
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.
- 4d ago First seen · 176 lines · 49 tokens per session scan A d7bfe297f8a4
find-session is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 1,885 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…