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/jhammant/ClaudeHistoryMCPWrote 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/jhammant/claudehistorymcp/claude-history)<a href="https://agentmods.dev/commands/jhammant/claudehistorymcp/claude-history"><img src="https://agentmods.dev/badge/commands/jhammant/claudehistorymcp/claude-history/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/jhammant/claudehistorymcp/claude-history"><img src="https://agentmods.dev/badge/commands/jhammant/claudehistorymcp/claude-history.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.00000 | $0.00430 |
| Opus 5 | $0.00000 | $0.00215 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
claude-history 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 12d 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
Claude History Search
Search and recall context from past Claude Code conversations.
Usage
/claude-history <query> # General search
/claude-history --solutions <error> # Find past error fixes
/claude-history --summary # Summarize last session for current project
/claude-history --patterns # Discover recurring patterns
/claude-history --context # Get full project context
/claude-history --projects # List all projects with history
Your Task
Parse the user's arguments and use the appropriate MCP tool from claude-history-mcp:
- If
--solutionsflag: Usefind_solutionstool with the remaining text aserror_or_problem - If
--summaryflag: Useget_session_summarytool with the current project - If
--patternsflag: Usefind_patternstool, optionally scoped to current project - If
--contextflag: Useget_project_contexttool with current project - If
--projectsflag: Uselist_projectstool - Otherwise: Use
search_historytool with the full text as the query
Presentation
Present results clearly:
- For search results: show project, date, and relevant excerpt
- For solutions: highlight the error → fix pattern
- For summaries: use structured format with sections
- For patterns: group by pattern type
If no results are found, suggest alternative search terms or broader queries.
Examples
# Search for Docker networking discussions
/claude-history docker network configuration
# Find how you fixed a specific error before
/claude-history --solutions ECONNREFUSED port 3000
# Get a summary of the last coding session
/claude-history --summary
# Find patterns in your React project
/claude-history --patterns project:react-app
# Search with date filter
/claude-history authentication after:7d
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.
- 12d ago First seen · 55 lines · 0 tokens per session scan A 5fca5613a37f
claude-history is a command published in the GitHub repository jhammant/ClaudeHistoryMCP (66 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 430 tokens. 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
screenshot
Screenshot a URL or document and read it visually.
add-memory
Add a new memory to the current project.
remember-this
Store a new memory in AgentMemory.
sessions
Manage Claude Code session history, aliases, and session metadata.
save-session
Save current session state to a dated file in /.claude/session-data/ so work can be resumed in a future session with full context.
timeline
Append-only project memory. Each project gets its own .timeline.json.