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 memtomem/memtomem --skill memtomem-handoffgit clone --depth 1 https://github.com/memtomem/memtomemWrote 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/memtomem/memtomem/memtomem-handoff)<a href="https://agentmods.dev/skills/memtomem/memtomem/memtomem-handoff"><img src="https://agentmods.dev/badge/skills/memtomem/memtomem/memtomem-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/memtomem/memtomem/memtomem-handoff"><img src="https://agentmods.dev/badge/skills/memtomem/memtomem/memtomem-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.00035 | $0.02340 |
| Opus 5 | $0.00017 | $0.01170 |
| Sonnet 5 | $0.00007 | $0.00468 |
| Haiku 4.5 | $0.00003 | $0.00234 |
Grade A, and why
memtomem-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 9d 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.
This is a copy
91% identical to handoff — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hand off project work
Derive the handoff operation (save or resume) from the current user request.
If the request does not clearly specify the handoff operation (save or resume), ask before calling a tool — and
in a non-interactive context (a subagent or scripted run with nobody to ask), do not
stall and do not guess: stop and report insufficient_input naming the missing handoff operation (save or resume).
A request that does specify the handoff operation (save or resume) proceeds normally in either context.
This workflow is explicit and sequential. It records a compact project handoff; it does not
capture the whole conversation, coordinate concurrent agents, or claim a task.
Accept exactly one operation: save or resume. If the operation is ambiguous, ask before
calling a tool; in a non-interactive context (a subagent or scripted run with nobody to
ask), do not stall and do not guess — stop and report insufficient_input: operation.
Supported runtime labels are claude-code, codex-cli, kimi-code,
opencode, and any. Infer the current runtime when possible; use any as the default target.
Common checks
-
Resolve the live Git root with
git rev-parse --show-toplevel. Stop if the current directory is not inside a Git worktree. -
Derive
project-slugfrom the Git-root directory name. Preserve case; replace each run of characters outside[A-Za-z0-9._-]with-and trim leading-characters. If the result is empty,.or.., ask for a valid slug instead of guessing. -
Use the namespace
shared:<project-slug>and callmem_statusonce. Verify that the status describes the intended database and project, and that this project's.memtomem/memories.localtier is registered. If it is not registered, stop and give:cd <project-root> && mm mem init --scope project_localNever fall back to
scope="user".
Save
Save records work that actually happened, so it is only valid where that work is known. Context
inherited from a caller or supplied in the request counts — the test is whether completed and
validation can be filled from something observed, not whether the run is interactive. Where
they cannot, do not save: a fabricated checkpoint is worse than none — stop and report
insufficient_input: work context. Resume has no such requirement.
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.
- 9d ago First seen · 147 lines · 35 tokens per session scan A 6499fbc36b18
memtomem-handoff is a skill published in the GitHub repository memtomem/memtomem (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 35 tokens to every session and 2,340 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to handoff, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
openclaw-memory-tencentdb-setup
A setup guide for installing, configuring, and checking a TencentDB memory plugin in OpenClaw, an agent environment.
cortex-distill
A skill for turning raw session records into organised notes and project documents. It uses a personal vault, which is a folder for storing and retrieving knowledge.
cortex-broadcast
Propagate insights from a distilled Raw into related existing Notes/Projects pages through conversational per-page edits.
cortex-query
A search tool for finding and retrieving information from Cortex, an external personal memory made up of stored notes and project pages.
cortex-evolve
A tool that saves technical notes and project decisions to a Cortex vault, which is an Obsidian note collection stored as files.
using-cortex
A guide for deciding when to search a Cortex vault, the user's personal store of notes, projects, weekly reports, and session records. It sends searches through the Cortex query process when the request refers to earlier work or an explicitly listed topic.