Claude-Mem, now presented as Grok Mem, records an agent's work, compresses it with AI, and brings relevant notes into later sessions so the agent can remember decisions and next steps. It is intended for persistent context across agent conversations and supports multiple coding-agent environments. The catalogue add-ons provide the workflows and integrations used to operate this memory system.
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 skills add thedotmack/claude-mem --skill handoffgit clone --depth 1 https://github.com/thedotmack/claude-memWrote 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/skills/thedotmack/claude-mem/handoff)<a href="https://agentmods.dev/skills/thedotmack/claude-mem/handoff"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/handoff/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/thedotmack/claude-mem/handoff"><img src="https://agentmods.dev/badge/skills/thedotmack/claude-mem/handoff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00066 | $0.01274 |
| Opus 5.5 | $0.00026 | $0.00510 |
| Sonnet 5.5 | $0.00013 | $0.00255 |
| Haiku 4.5 | $0.00007 | $0.00127 |
Grade A, and why
handoff 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 15d 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.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Generate a structured HANDOFF.md file that gives a fresh Claude session everything it needs to continue this work without dragging the current degraded context forward.
claude-mem already injects recent observations into every new session, so the fresh agent starts with a timeline of what happened. The handoff adds what that timeline cannot: the goal, the failed attempts and why they failed, the current theory, and exact next steps, plus pointers into memory for deeper recall.
When to Use
- The session is long and Claude feels confused or repetitive
- Claude keeps trying the same failing solution over and over
- The user wants to step away and resume later
/compactran but Claude still lacks clear direction- The user says "handoff", "generate a handoff", "I want to start fresh", or "write a handoff doc"
What to Capture
Think hard about the full arc of this conversation before writing. The handoff must be useful to a Claude instance that has never seen this conversation.
Required Sections
-
Goal — One paragraph. What is the user actually trying to accomplish? State the end state, not the current sub-task. Be specific enough that a fresh agent can orient immediately.
-
Current State — What is working right now? What is broken? What is the exact symptom of the problem? Include error messages verbatim if relevant.
-
Files in Play — List every file that has been read, edited, or created during this session that is relevant to the current task. Use absolute or repo-relative paths. Include a one-line note on why each file matters.
-
What Has Been Tried (and Why It Failed) — This is the most important section. List every approach attempted that did not work, and explain WHY it failed (not just that it failed). A fresh agent that skips this section will repeat the same mistakes.
-
Current Best Theory — What do you currently believe is the right path forward, even if you haven't proven it yet? Include any evidence or reasoning that supports it.
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.
- 15d ago First seen · 122 lines · 66 tokens per session scan A 9c1ad95a780f
handoff is a skill published in the GitHub repository thedotmack/claude-mem (101,048 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 1,274 once invoked, about $0.0003 per session on Opus 5.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-10-01.
Other skills, from other repositories
hivemind-memory
Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.
hivemind-memory
Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.
hivemind
Global team and org memory powered by Activeloop. ALWAYS check BOTH built-in memory AND Hivemind memory when recalling information.
dejavu-rules
A conversation-based manager for rules stored in CLAUDE.md, a project file that tells the coding assistant how to work. It can add, edit, remove, and review those rules.
dejavu
Review and manage learned antipattern rules. Use when Claude should review its past mistakes, apply learned rules to CLAUDE.md, or check rule effectiveness. Triggers on "/dejavu", "review rules", "what did you learn".
dejavu-report
Generate a weekly report of detected patterns and rule effectiveness. Use when user asks "dejavu report", "what did you learn this week", "dejavu weekly".