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 kirill-sviridov/handoff-mcp --skill handoffgit clone --depth 1 https://github.com/kirill-sviridov/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/kirill-sviridov/handoff-mcp/handoff)<a href="https://agentmods.dev/skills/kirill-sviridov/handoff-mcp/handoff"><img src="https://agentmods.dev/badge/skills/kirill-sviridov/handoff-mcp/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/kirill-sviridov/handoff-mcp/handoff"><img src="https://agentmods.dev/badge/skills/kirill-sviridov/handoff-mcp/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.00156 | $0.01216 |
| Opus 5 | $0.00078 | $0.00608 |
| Sonnet 5 | $0.00031 | $0.00243 |
| Haiku 4.5 | $0.00016 | $0.00122 |
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 12d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session hand-off with handoff-mcp
This skill encodes when to use the handoff-mcp memory tools. The tools
themselves (get_brief, log_event, checkpoint, search_memory,
note_entity) describe what they do; this skill is the workflow around them.
If the handoff-mcp tools are not available, tell the user the MCP server isn't connected and stop — do not fabricate memory.
0. Setup — make sure this project has a memory instruction file
The first time you use handoff-mcp in a project, check that the project's agent-instruction file tells future sessions to use memory — otherwise an agent that hasn't loaded this skill (or a different client) won't know to. Pick the file your client reads:
| Client | File |
|---|---|
| Claude Code / Desktop | CLAUDE.md |
| Codex / generic agents | AGENTS.md |
| Cursor | .cursor/rules/handoff.mdc (or legacy .cursorrules) |
| Windsurf | .windsurfrules |
If that file is missing, or has no handoff section, create/append this block (don't duplicate it, don't clobber existing content):
## Memory (handoff-mcp)
At the START of a session, call `get_brief` and resume from the next step —
don't redo settled decisions or repeat recorded dead-ends. As we work,
proactively `log_event` goals/decisions(+why)/dead-ends/files/questions/next step
— ONE atomic item per call (1-2 sentences), not a session summary; reference
durable notes inline as `[[Entity]]`. If a decision is reversed, log the new one
with `supersedes` = the old id. On "stopping / го дальше / на сегодня всё" call
`checkpoint`. When the user mentions past or other-project work, `search_memory`.
1. At the start of a session — load context first
Before doing substantive work on a project, call get_brief to load the
prior session's goal, next step, key decisions, dead-ends, open questions, and
related knowledge. Briefly orient the user ("Resuming: last time you …; next
step was …") and continue from the next step. Do not redo settled decisions
or repeat recorded dead-ends.
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.
- 12d ago First seen · 98 lines · 156 tokens per session scan A 89b9f16cd614
session-handoff is a skill published in the GitHub repository kirill-sviridov/handoff-mcp (2 stars, last pushed 2mo ago), licensed MIT. It adds 156 tokens to every session and 1,216 once invoked, about $0.0008 per session on Opus 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.