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.
git clone --depth 1 https://github.com/HelloRuru/claude-memory-engineWrote 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/commands/helloruru/claude-memory-engine/handoff)<a href="https://agentmods.dev/commands/helloruru/claude-memory-engine/handoff"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/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/commands/helloruru/claude-memory-engine/handoff"><img src="https://agentmods.dev/badge/commands/helloruru/claude-memory-engine/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.00011 | $0.00311 |
| Opus 5.5 | $0.00004 | $0.00124 |
| Sonnet 5.5 | $0.00002 | $0.00062 |
| Haiku 4.5 | $0.00001 | $0.00031 |
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 1mo 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.
What it actually says
Session Handoff
Generate a handoff file so another Claude Code session can continue where this one left off.
Steps
-
Analyze current session — What are you working on right now? What files have been modified? What decisions were made?
-
Write handoff file — Save to the project's memory directory as
handoff-{topic}.mdwith this format:
---
name: handoff-{topic}
description: {one-line summary of what needs to be handed off}
type: project
---
# {Title} Handoff
**Status:** {what's done / what's pending}
**Date:** {today}
## What was done
{bullet list of completed work}
## What's left to do
- [ ] {pending task 1}
- [ ] {pending task 2}
## Key decisions
{any decisions the next session needs to know about}
## Files modified
{list of files changed in this session}
- Confirm — Tell the user the handoff file has been saved and will be automatically detected by the next session.
How it works
- SessionStart hook automatically reads all unread
handoff-*.mdfiles when a new conversation starts - memory-sync hook detects new handoff files appearing mid-conversation and alerts immediately
- Handoff files are tracked in
.handoff-read.jsonso they're only shown once
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.
- 1mo ago First seen · 48 lines · 11 tokens per session scan A f03e2d127bd5
handoff is a command published in the GitHub repository HelloRuru/claude-memory-engine (134 stars, last pushed 5mo ago), licensed MIT. It adds 11 tokens to every session and 311 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
watch
You are executing the /hydra:watch command. Live monitoring of all background agents with real-time status updates.
golden-path
The golden path. One command, idea to merged PR. Runs the full pipeline, prd → prp → plan → dev → test → pr, with sensor + eval gates at every stage.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
render
Inspect an archived transcript (gzipped) — show counts, tool calls, errors. Useful after a PreCompact or SessionEnd, before deciding to write a retroactive /continuum:checkpoint.