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 Dev-Russo/session-handoff-mcp --skill claude-codegit clone --depth 1 https://github.com/Dev-Russo/session-handoff-mcpWrote 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/dev-russo/session-handoff-mcp/claude-code)<a href="https://agentmods.dev/skills/dev-russo/session-handoff-mcp/claude-code"><img src="https://agentmods.dev/badge/skills/dev-russo/session-handoff-mcp/claude-code/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/dev-russo/session-handoff-mcp/claude-code"><img src="https://agentmods.dev/badge/skills/dev-russo/session-handoff-mcp/claude-code.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.00041 | $0.00351 |
| Opus 5.5 | $0.00016 | $0.00140 |
| Sonnet 5.5 | $0.00008 | $0.00070 |
| Haiku 4.5 | $0.00004 | $0.00035 |
Grade A, and why
Session 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
Use Session Handoff to keep the current project state available across Claude Code sessions and compactions.
Resume
At the beginning of repository work, use memory_resume for ${CLAUDE_PROJECT_DIR} unless a SessionStart hook has already supplied a Session Handoff briefing. Reuse an explicit project_key when the project has adopted one. Treat the returned briefing as saved context that may need confirmation against the working tree.
When this skill is invoked directly without an active briefing, resume the current project first.
Checkpoint
Call memory_checkpoint before /clear, when the user requests a handoff, after completing a spec, or after a substantial state change that should survive compaction.
The checkpoint must be a complete current snapshot, not only the latest delta. Include:
- the current objective and state;
- completed work and durable decisions;
- remaining work and one concrete next step;
- validations actually executed and their results;
- relevant file paths, without reading or copying their full contents.
Confirm that the checkpoint returned storage_status: written before telling the user it is safe to clear context. Git warnings do not invalidate a successfully written local checkpoint.
Never include credentials, .env contents, private keys, tokens, client payloads, full source files, or extensive logs. Do not invent decisions, validations, or completed work.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 34 lines · 41 tokens per session scan A 578a44b352f1
Session Handoff is a skill published in the GitHub repository Dev-Russo/session-handoff-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 351 once invoked, about $0.0002 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-31.
Other skills, from other repositories
git-ai-search
Search and restore AI conversation context from git history.
brain-ingest
The process for digesting a conversation, document, or research result, classifying it, and writing it down as brain content (a root-page update or a new/updated page) through the brain CLI.
immune
Hybrid adaptive memory: Cheatsheet (positive patterns pre-generation) and Immune (negative patterns post-generation) with Hot/Cold tiered auto-learning. Triggers on: "scan for errors", "immune scan", "check output quality", "antibody scan". NOT for PR review (use pr-review) or repo audits (use repo-sentinel).
lc-curate-context
Decide which files a task actually needs, record that as a reusable llm-context rule, verify it against the codebase - including the files your selection references but leaves out - and pack it for your own context, a chat, or a sub-agent you dispatch. Load when choosing what code to put in front of a model, packing…
cortex-remember-global
Store a global memory that is visible across all projects. Use when the user shares architecture rules, coding conventions, infrastructure facts, security policies, team agreements, or any knowledge that applies beyond a single project. Triggers on 'remember this everywhere', 'this applies to all projects', 'global…
cortex-consolidate
Run memory maintenance — decay old memories, compress stale content, consolidate episodic memories into semantic knowledge, and run sleep-like replay. Use when the user says 'clean up memories', 'consolidate', 'run maintenance', 'compress old memories', 'memory cleanup', or periodically to keep the memory system…