recover

A command that restores the agent's memory files from a GitHub backup. It can also copy newer memory files from that backup to projects on another device.

In plain words
What is it for?
Pulling a memory backup from GitHub, distributing it to local projects, and recovering after a computer change, deleted files, or a broken startup hook.
Why use it?
It helps recover local memory after files are deleted or damaged and keeps memory available when working across computers.

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/helloruru/claude-memory-engine/recover
Clone the repo
git clone --depth 1 https://github.com/HelloRuru/claude-memory-engine
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 417 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.00000 $0.00417
Opus 5 $0.00000 $0.00209
Sonnet 5 $0.00000 $0.00083
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

recover 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/recover.md · 41 lines

What it actually says

/recover -- Disaster Recovery + Cross-Device Sync

Restore memory from your GitHub backup when local memory files are lost or corrupted. Also works for cross-device sync.

Prerequisites

You need a GitHub repo set up as your memory backup (the one you push to with /backup or /sync). If you haven't created a backup repo yet, this command won't work.

Cross-Device Sync (v1.6)

bash ~/.claude/scripts/hooks/memory-backup.sh pull

The pull mode does two things:

  1. git pull from GitHub to get the latest
  2. Distribute repo/memory/*.md into every local project directory that has a memory/ folder (newer file wins, won't overwrite local changes)

This solves the "Device A pushed but Device B can't see it" problem -- each device has different working directories, so projects/ paths differ. Global memory must be actively distributed.

When to Use

  • Switched to a new computer and need to bring over memories from another device
  • Local memory files were accidentally deleted
  • SessionStart hook isn't working
  • Memory files appear corrupted or empty
  • Another device pushed new memory and you want to pick it up (for routine use, /sync is more convenient)

Steps

  1. Protect current state -- Run /backup first to push any remaining local changes
  2. Pull from GitHub -- bash ~/.claude/scripts/hooks/memory-backup.sh pull
  3. Verify -- Read MEMORY.md, scan all index entries
  4. Report -- "Recovered! Found {N} index entries, {M} memory files"

Notes

  • Under normal conditions, SessionStart hook auto-loads the last session summary + recent memory changes. You should NOT need this command regularly
  • This is the "break glass" option for when the automated system fails
  • Always push before pulling to avoid overwriting local changes
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 · 41 lines · 0 tokens per session scan A 3c1909ab3961

Subscribe to this mod's changes

recover is a command published in the GitHub repository HelloRuru/claude-memory-engine (133 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 417 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-30.