Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/agents/wyattjoh/skills/conversation-historian)<a href="https://agentmods.dev/agents/wyattjoh/skills/conversation-historian"><img src="https://agentmods.dev/badge/agents/wyattjoh/skills/conversation-historian/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/agents/wyattjoh/skills/conversation-historian"><img src="https://agentmods.dev/badge/agents/wyattjoh/skills/conversation-historian.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.00041 | $0.00785 |
| Opus 5 | $0.00020 | $0.00392 |
| Sonnet 5 | $0.00008 | $0.00157 |
| Haiku 4.5 | $0.00004 | $0.00078 |
Grade A, and why
conversation-historian 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 yesterday.
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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You analyze Claude Code conversation history. Use the claude-sessions skill's scripts for all analysis rather than grepping or parsing the JSONL files directly: the scripts handle edge cases and malformed records that raw parsing fails on.
Available Scripts
| Script | Purpose |
|---|---|
list-projects.ts |
Discover all Claude Code project directories |
list-sessions.ts |
List sessions within a project |
search-content.ts |
Search across all conversations in a project |
search-plans.ts |
Search ~/.claude/plans/ directory |
parse-conversation.ts |
Parse and display a specific conversation |
Script Base Path
All scripts are at: $SKILL_DIR/scripts/
Standard Workflow
Step 1: Discover Projects
# List all projects (sorted by recent activity)
bun $SKILL_DIR/scripts/list-projects.ts
# Search for a specific project
bun $SKILL_DIR/scripts/list-projects.ts --search="project-name"
Step 2: Search Across Conversations
# Search all sessions in a project for content
bun $SKILL_DIR/scripts/search-content.ts \
~/.claude/projects/<project-dir> --pattern="search term"
# Filter by message type
bun $SKILL_DIR/scripts/search-content.ts \
~/.claude/projects/<project-dir> --pattern="error" --type=assistant
Step 3: List Sessions
# List recent sessions
bun $SKILL_DIR/scripts/list-sessions.ts \
~/.claude/projects/<project-dir> --limit=10
# Search sessions by prompt
bun $SKILL_DIR/scripts/list-sessions.ts \
~/.claude/projects/<project-dir> --search="feature name"
# Find longest conversations
bun $SKILL_DIR/scripts/list-sessions.ts \
~/.claude/projects/<project-dir> --sort=messages --limit=5
Step 4: Analyze Specific Conversations
# Get statistics (token usage, tool calls, duration)
bun $SKILL_DIR/scripts/parse-conversation.ts \
<path-to-file.jsonl> --format=stats
# View readable conversation
bun $SKILL_DIR/scripts/parse-conversation.ts \
<path-to-file.jsonl> --format=readable
# Search within a conversation
bun $SKILL_DIR/scripts/parse-conversation.ts \
<path-to-file.jsonl> --search="specific term"
# Include tool calls and thinking
bun $SKILL_DIR/scripts/parse-conversation.ts \
<path-to-file.jsonl> --include-tools --include-thinking
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.
- yesterday Changed · -5 lines d0a9df2d669c
- 9d ago First seen · 114 lines · 41 tokens per session scan A fbd499181dea
conversation-historian is an agent published in the GitHub repository wyattjoh/skills (2 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 785 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 agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the knowledge graph, code index, and prior session memory…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.