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 Vertiso/memory-vscode --skill handoff-resumegit clone --depth 1 https://github.com/Vertiso/memory-vscodeWrote 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/vertiso/memory-vscode/handoff-resume)<a href="https://agentmods.dev/skills/vertiso/memory-vscode/handoff-resume"><img src="https://agentmods.dev/badge/skills/vertiso/memory-vscode/handoff-resume/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/vertiso/memory-vscode/handoff-resume"><img src="https://agentmods.dev/badge/skills/vertiso/memory-vscode/handoff-resume.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.00049 | $0.00474 |
| Opus 5.5 | $0.00020 | $0.00190 |
| Sonnet 5.5 | $0.00010 | $0.00095 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
handoff-resume 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 18d 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
Handoff Resume
Resume a prior session from a handoff — verifying before operating.
Announce: "Using the handoff-resume skill to pick up a prior session."
CLI fallback: when you call vmem through the vmem CLI instead of the MCP tools, run it as
vmem --agent vscode <command>, so your writes are attributed to this client.
When to use
- The user runs
/handoff-resume. helloreported open handoffs at session start.
Procedure
- Call
handoff_resume(the MCP tool, orvmem --agent vscode handoff-resume) with noclaimargument — this returns the live set of open handoffs. - Branch on the count:
- 0 — nothing to resume; stop here.
- 1 — carry it forward.
- >1 — interactive pick: present one option per handoff (its scope, the writing agent, a one-line state), pre-flagging any that look stale; let the user choose.
- Claim the chosen handoff — call
handoff_resumeagain withclaim: <id>. Claiming archives it so a parallel session resuming concurrently cannot re-grab it. - Do the recipient diligence the handoff's slot-6 advisory calls for, before operating. Verify the slot-3 "where it stands" state against current reality. Re-confirm any decision or approval recorded in slot 2. The handoff carries its claims honestly, but the world may have moved.
- Present the reconciled picture and the concrete pick-up point to the user.
Why verify
The handoff author distinguished what was done from what was believed, but cannot know what changed since. Verification is the recipient's job — do it before you operate, not after.
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.
- 18d ago Changed · +3 lines b4ec404e5d42
- 1mo ago First seen · 44 lines · 49 tokens per session scan A 56c7d4430480
handoff-resume is a skill published in the GitHub repository Vertiso/memory-vscode (0 stars, last pushed 2d ago), licensed MIT. It adds 49 tokens to every session and 474 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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
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…