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.
git clone --depth 1 https://github.com/stefan-jansen/claude-code-toolkitWrote 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/stefan-jansen/claude-code-toolkit/search)<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/search"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/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.
<a href="https://agentmods.dev/commands/stefan-jansen/claude-code-toolkit/search"><img src="https://agentmods.dev/badge/commands/stefan-jansen/claude-code-toolkit/search.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00011 | $0.00965 |
| Opus 5.5 | $0.00004 | $0.00386 |
| Sonnet 5.5 | $0.00002 | $0.00193 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory:search [query]
Search Claude Code's session history to find past decisions, discussions, and context.
How It Works
Claude Code automatically stores complete session history in ~/.claude/projects/. This command searches that history to recover:
- Past decisions and their rationale
- Discussions about specific topics
- Auto-compact summaries
- Tool calls and their results
Usage
/memory:search "authentication approach"
/memory:search "database schema" --summaries-only
/memory:search "bug fix" --recent 5
Arguments
query- Keywords to search for (required)--summaries-only- Only search auto-compact summaries (faster, less detail)--recent N- Only search N most recent sessions (default: 20)
Implementation
When invoked, execute:
#!/bin/bash
QUERY="$1"
PROJECT_DIR=$(pwd)
CLAUDE_PROJECT="-$(echo "$PROJECT_DIR" | sed 's|^/||; s|/|-|g')"
SESSION_DIR="$HOME/.claude/projects/$CLAUDE_PROJECT"
if [ ! -d "$SESSION_DIR" ]; then
echo "No session history found for this project."
exit 1
fi
echo "Searching session history for: $QUERY"
echo ""
# Search summaries first (fast overview)
echo "## Relevant Summaries"
for f in $(ls -t "$SESSION_DIR"/*.jsonl | head -20); do
grep -i "$QUERY" "$f" 2>/dev/null | \
jq -r 'select(.type=="summary") | .summary' 2>/dev/null
done | sort -u | head -15
echo ""
echo "## Key Discussions"
# Search user messages and assistant responses
for f in $(ls -t "$SESSION_DIR"/*.jsonl | head -10); do
DATE=$(stat -c %y "$f" | cut -d' ' -f1)
# Check if file matches
if grep -qi "$QUERY" "$f"; then
echo ""
echo "### Session: $DATE"
# Extract relevant assistant text (decisions, recommendations)
grep -i "$QUERY" "$f" | \
jq -r 'select(.type=="assistant") | .message.content[]? |
select(.type=="text") | .text' 2>/dev/null | \
grep -i "$QUERY" | \
grep -iE "(decided|chose|recommend|should|will use|verdict|conclusion|the answer|solution)" | \
head -5
fi
done
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.
- 1mo ago First seen · 139 lines · 11 tokens per session scan A 9d987c198847
search is a command published in the GitHub repository stefan-jansen/claude-code-toolkit (90 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 965 once invoked, about $0.0000 per session on Opus 5.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-30.
Other commands, from other repositories
ctx
Search agent history or trace code to its original agent session.
context-stats
Display context window usage and token statistics.
learn
A command for recording lessons learned from direct notes, recent errors, or the current work session. It can classify lessons, suggest automations from git history, and manage the saved list.
handoff
Write a session handoff document for continuity.
revise-claude-md
Update CLAUDE.md with learnings from this session.
session-save
Save the current session state — decisions, modified files, current status, and next steps — to a handoff file for later resume.