recall-loop

A scheduled memory digest command for Claude Code. It shows memories saved recently and pending to-dos from Recall, a memory system, over a chosen time window.

In plain words
What is it for?
Use it with Claude Code’s /loop scheduler to review the last 30, 60, or 120 minutes, or another specified window.
Why use it?
It reduces the need to manually check recent decisions and outstanding work, and highlights overdue to-dos during recurring check-ins.

Command

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/joseairosa/recall/loop
Clone the repo
git clone --depth 1 https://github.com/joseairosa/recall
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 443 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.

ModelPer sessionOnce invoked
Fable 5 $0.00036 $0.00443
Opus 5 $0.00018 $0.00221
Sonnet 5 $0.00007 $0.00089
Haiku 4.5 $0.00004 $0.00044

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

Security

Grade A, and why

recall-loop 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.

claude-plugin/commands/loop.md · 58 lines

What it actually says

/recall-loop

Run a periodic digest of your Recall memory. Shows what was stored recently and any pending to-dos. Designed to be scheduled with /loop.

Usage

/recall-loop                  # Digest of last 60 minutes (default)
/recall-loop 30               # Digest of last 30 minutes
/recall-loop 120              # Digest of last 2 hours

Scheduling with /loop

/loop 30m /recall-loop        # Check in every 30 minutes
/loop 1h /recall-loop         # Hourly digest
/loop 2h /recall-loop 120     # Every 2 hours, look back 2 hours

What it shows

  • Recent memories — decisions, patterns, insights stored in the window
  • Pending to-dos — overdue and high-priority items that need attention

Behavior

  1. Parse the optional window_minutes argument (default: 60)
  2. Call mcp__recall-remote__loop_digest with { window_minutes, include_todos: true }
  3. Present the formatted digest
  4. If overdue to-dos exist, surface them prominently

Example output

Recall Digest — Last 60m [14:30:00]
==================================================
MEMORIES  3 new
  [decision] Chose Redis for session caching with 30-minute TTL
  [insight] Auth middleware reads tenant context from req.tenant
  [code_pattern] Always use generateUlid() for new IDs

TO-DOS
  [OVERDUE] Review security audit report (high)
  Write tests for billing service (medium)

--------------------------------------------------
Tip: /loop 60m /recall-loop
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. 2d ago First seen · 58 lines · 36 tokens per session scan A 9b0813ba87c7

Subscribe to this mod's changes

recall-loop is a command published in the GitHub repository joseairosa/recall (175 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 443 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-30.