recall

recall is a command for Claude Code from tony/claude-code-riper-5. It costs 8 tokens per session (499 once invoked), scanned B, original, MIT.

A command that retrieves saved notes from the current Git branch’s memory folder. Git branches are separate lines of work within a software project.

In plain words
What is it for?
Reviewing past session notes, checking recent commits, and restoring context for work on the current branch.
Why use it?
It brings back earlier project context and recent changes so you do not have to reconstruct them from memory.

Command for Claude Code

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/tony/claude-code-riper-5/recall
Clone the repo
git clone --depth 1 https://github.com/tony/claude-code-riper-5

Made for: Claude Code.

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.

agentmods badge for recall

README.md
[![agentmods](https://agentmods.dev/badge/commands/tony/claude-code-riper-5/recall.svg)](https://agentmods.dev/commands/tony/claude-code-riper-5/recall)
Your own site
<a href="https://agentmods.dev/commands/tony/claude-code-riper-5/recall"><img src="https://agentmods.dev/badge/commands/tony/claude-code-riper-5/recall.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 499 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00008 $0.00499
Opus 5 $0.00004 $0.00249
Sonnet 5 $0.00002 $0.00100
Haiku 4.5 $0.00001 $0.00050

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

Security

Grade B, and why

recall scanned grade B with 1 finding 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

- Memory-bank MUST be at repository root: Use `git rev-parse --show-toplevel` to find root, then `[ROOT]/.claude/memory-bank/`
.claude/commands/memory/recall.md · 50 lines

What it actually says

Recalling from Memory Bank

I'll retrieve memories from the branch-aware memory bank.

⚠️ Memory Bank Location Requirements

CRITICAL PATH POLICY:

  • Memory-bank MUST be at repository root: Use git rev-parse --show-toplevel to find root, then [ROOT]/.claude/memory-bank/
  • NEVER create package-level memory-banks: packages/*/.claude/memory-bank/
  • In monorepos: ONE memory-bank at root serves entire project

Correct vs Incorrect Paths for Recall

Correct: [ROOT]/.claude/memory-bank/main/session.md (where ROOT = git rev-parse --show-toplevel) ❌ Wrong: [ROOT]/packages/react/.claude/memory-bank/main/session.mdWrong: packages/react/.claude/memory-bank/main/session.md

Current Context

  • Branch: !git branch --show-current
  • Date: !date +%Y-%m-%d

Git History Since Last Session

Show commits since last memory save:

last_memory=$(ls -t $(git rev-parse --show-toplevel)/.claude/memory-bank/$(git branch --show-current)/sessions/*.md 2>/dev/null | head -1)
if [ -n "$last_memory" ]; then
    last_date=$(stat -c %y "$last_memory" | cut -d' ' -f1)
    git log -n 10 --oneline --since="$last_date"
fi

Show recent changes to memory bank:

git log -n 5 -p -- .claude/memory-bank/

Search Scope

Looking for memories in: [ROOT]/.claude/memory-bank/!git branch --show-current/ (where ROOT = git rev-parse --show-toplevel)

Search Query

$ARGUMENTS

Available Memories

!ls -la $(git rev-parse --show-toplevel)/.claude/memory-bank/$(git branch --show-current)/ 2>/dev/null || echo "No memories found for current branch"

I'll search for and display relevant memories based on your query, along with git history context since the last session.

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.

  1. 5d ago First seen · 50 lines · 8 tokens per session scan B d34f28e6fdb9

Subscribe to this mod's changes

recall is a command published in the GitHub repository tony/claude-code-riper-5 (93 stars, last pushed 19d ago), licensed MIT. It adds 8 tokens to every session and 499 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.