A command for searching stored records of earlier coding sessions. It can search all saved sessions or limit results to the current project, with an option to show more detailed content.

Use it to find previous sessions by topic, restrict the search to a project, request detailed results, set a result limit, or return results as JSON or Markdown.

It saves time when useful decisions, fixes, or code examples are buried in past conversations. Instead of reconstructing earlier context, you can search for terms such as an authentication issue or database migration.

recall — Command by ErebusEnigma

Install

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.

agentmods

npx agentmods add commands/erebusenigma/context-memory/recall

Clone the repo

git clone --depth 1 https://github.com/ErebusEnigma/context-memory

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 859 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00007	$0.00859
Opus 5	$0.00003	$0.00430
Sonnet 5	$0.00001	$0.00172
Haiku 4.5	$0.00001	$0.00086

Measured 2d ago against content hash d5f8ee4767ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

recall 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 2d 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.

commands/recall.md · 139 lines

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.

/recall Command

Search past sessions stored in context memory.

Usage

/recall <query> [options]

Arguments:

query (required): Search terms to find relevant sessions

Options:

--project: Limit search to current project only
--detailed: Include full message content and code snippets
--limit N: Maximum number of results (default: 10)
--format: Output format: json or markdown (default: markdown)

Examples

/recall authentication
/recall "database migration" --project
/recall jwt --detailed --limit 5
/recall "error handling" --project --detailed

Workflow

When the user runs /recall:

Parse Query and Options

Extract the search query and any flags:
- --project -> filter by current project path
- --detailed -> include tier 2 content
- --limit N -> cap results

Execute Search

Run the search script:

python "~/.claude/skills/context-memory/scripts/db_search.py" "<query>" [--project "$(pwd)"] [--detailed] [--limit N] --format markdown

Present Results

Display results in a clear, scannable format:

# Context Memory Results
**Query**: "authentication"
**Results**: 3 sessions

---
## 1. 2026-01-15 | my-app (Match #1)
**Summary**: Implemented JWT auth with refresh token rotation
**Topics**: authentication, JWT, security, Node.js
**Decisions**:
- Use RS256 for token signing
- 15-minute access token expiry

<details><summary>Full Context</summary>
[Detailed content when --detailed flag is used]
</details>

Offer Follow-up Actions

If results are helpful, offer to:
- Show more details for a specific session
- Apply learnings from a past session to current work
- Search with different terms
If results are insufficient:
- Suggest broader search terms
- Offer to search in messages (deeper search)
- Suggest removing --project filter

Search Tips

The search uses FTS5 full-text search with Porter stemming:

Read the full file on GitHub · 139 lines

Changes

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.

2d ago First seen · 139 lines · 7 tokens per session scan A d5f8ee4767ff

Subscribe to this mod's changes

recall is a command published in the GitHub repository ErebusEnigma/context-memory (5 stars, last pushed 6mo ago), licensed MIT. It adds 7 tokens to every session and 859 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.

Databases Memory and context Writing and docs claude-code claude-code-plugin context full-text-search plugin

recall

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/recall Command

Usage

Examples

Workflow

Search Tips

What this file has done since we first saw it

Other commands, from other repositories

recall

preview

restore

share-to-pr

switch

diff