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/xiaolai/echo-sleuth-for-claude/extractgit clone --depth 1 https://github.com/xiaolai/echo-sleuth-for-claudeWrote 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/xiaolai/echo-sleuth-for-claude/extract)<a href="https://agentmods.dev/commands/xiaolai/echo-sleuth-for-claude/extract"><img src="https://agentmods.dev/badge/commands/xiaolai/echo-sleuth-for-claude/extract.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.00000 | $0.00567 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
extract 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 5d 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
Extract durable knowledge from a past Claude Code conversation session.
Arguments: $ARGUMENTS
Step 1: Find the session
If a session-id UUID is provided, locate it directly. Otherwise, list recent sessions:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/list-sessions.sh" current --limit 7 --since "$(date -v-7d +%Y-%m-%d 2>/dev/null || date -d '7 days ago' +%Y-%m-%d)"
Present the list and ask the user which session to extract from (or default to the most recent).
Step 2: Run extraction
bash "${CLAUDE_PLUGIN_ROOT}/scripts/extract-knowledge.sh" SESSION_JSONL_PATH
This outputs a JSON array of candidate extractable items, each with:
category: value | decision | correction | pattern | lesson | referencecontent: summary texttimestamp: when it occurredsuggested_destination: memory | claude_md | knowledge_file | skipsuggested_type: value | user | feedback | project | reference
Step 3: Present items to user
For each item, present:
- The category and content
- The suggested destination and type
- Ask the user to choose:
- Memory — save as a memory file (ask for name if not obvious)
- CLAUDE.md — add to project's CLAUDE.md instructions
- Knowledge file — save as human-readable markdown (ask for path, default: docs/knowledge/)
- Skip — discard
Step 4: Write approved items
For each approved item, write to the chosen destination:
Memory file: Create ~/.claude/projects/<project>/memory/<name>.md with frontmatter:
---
name: <name>
description: <one-line summary>
type: <chosen type>
---
<content>
Then append an entry to MEMORY.md. If MEMORY.md doesn't exist, create it. If only a standalone MEMORY.md exists (no individual files), create the first individual file and convert MEMORY.md to an index.
CLAUDE.md: Append to the project's CLAUDE.md at the resolved project root. If project root is unresolvable, offer memory file as fallback.
Knowledge file: Write markdown to the chosen path.
Step 5: Summary
Report what was extracted and where it was saved.
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.
- 5d ago First seen · 67 lines · 0 tokens per session scan A 6ce3c6e97d08
extract is a command published in the GitHub repository xiaolai/echo-sleuth-for-claude (9 stars, last pushed 11d ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 567 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-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.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
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.