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 commands/iam-dev/cc-sessions/sessions-searchgit clone --depth 1 https://github.com/iam-dev/cc-sessionsWrote 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/commands/iam-dev/cc-sessions/sessions-search)<a href="https://agentmods.dev/commands/iam-dev/cc-sessions/sessions-search"><img src="https://agentmods.dev/badge/commands/iam-dev/cc-sessions/sessions-search.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.00009 | $0.00426 |
| Opus 5 | $0.00005 | $0.00213 |
| Sonnet 5 | $0.00002 | $0.00085 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
sessions: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 3d 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.
What it actually says
Search Sessions
Full-text search across all saved session memories.
Usage Examples
/sessions:search authentication
/sessions:search "bug fix" --project ./myapp
/sessions:search refactor --from "last month"
Instructions
When the user runs /sessions:search <query>, execute the search via CLI:
node "${CLAUDE_PLUGIN_ROOT}/dist/cli.js" search "$ARGUMENTS"
Parse arguments from user input:
$1- The search query (required)--project- Limit search to specific project path--from- Start date filter--to- End date filter
Output Format
Search: "{query}"
Found {count} sessions:
┌─────────────────────────────────────────────────────────────────┐
│ 1. {summary} │
│ {date} - {duration} - {tokens} tokens - {project} │
│ "...matched text with highlights..." │
├─────────────────────────────────────────────────────────────────┤
│ 2. {summary} │
│ {date} - {duration} - {tokens} tokens - {project} │
│ "...matched text with highlights..." │
└─────────────────────────────────────────────────────────────────┘
Enter number to view details, or use /sessions:resume <id> to resume.
No Results Message
Search: "{query}"
No sessions found matching your search.
Suggestions:
- Try broader search terms
- Check spelling
- Remove date filters to search all time
- Use /sessions:list to browse all sessions
Search Tips
- Search is case-insensitive
- Partial word matches are supported
- Multiple words are treated as AND (all must match)
- Use quotes for exact phrases: "user authentication"
- Search covers: summary, description, tasks, files, messages
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.
- 3d ago First seen · 73 lines · 9 tokens per session scan A 2f12bbbada27
sessions:search is a command published in the GitHub repository iam-dev/cc-sessions (2 stars, last pushed 4mo ago), licensed MIT. It adds 9 tokens to every session and 426 once invoked, about $0.0000 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.