Borrowing it
Nothing to install: this file belongs to rakovi4/continue-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rakovi4/continue-framework/main/.claude/skills/handoff/SKILL.mdgit clone --depth 1 https://github.com/rakovi4/continue-frameworkWrote 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/rakovi4/continue-framework/handoff)<a href="https://agentmods.dev/skills/rakovi4/continue-framework/handoff"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/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/rakovi4/continue-framework/handoff"><img src="https://agentmods.dev/badge/skills/rakovi4/continue-framework/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00080 | $0.00846 |
| Opus 5.5 | $0.00032 | $0.00338 |
| Sonnet 5.5 | $0.00016 | $0.00169 |
| Haiku 4.5 | $0.00008 | $0.00085 |
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 2mo 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handoff - Preserve Conversation Context
Run this to persist what a future session would otherwise lose. /handoff runs automatically the moment the agent observes something worth noting during work, and manually before /clear or /compact as a final sweep. /handoff is the ONLY writer of journey summaries and carryover.
Workflow
- Identify the work item -- find the story or task the conversation worked on (recent git log
Story N/Task N, or theprogress.mdthat changed). Resolve its folder. - Locate the last work-unit commit -- the conversation since that commit is the review window. Everything after it (discussion, debugging, decisions) is what
/handoffcaptures; the work unit itself is already recorded inprogress.mdand its commit. - Review the window against the "When to Write" triggers in
.claude/templates/workflow/summary-format.md. Decide, per trigger, whether anything noteworthy happened. - Write entries, or nothing -- if at least one trigger fired, append entries to the summary file (see File Layout) in the strict format from
.claude/templates/workflow/summary-format.md. Before appending, check the file for an entry already covering the same moment and skip it --/handoffruns many times per conversation and must not duplicate. If nothing fired, or every fired trigger is already recorded, create no file and append no line -- report "nothing to record". - Promote carryover -- if a scenario's last step is now
[x](scenario complete), promote codebase-quirk and system-invariant entries from that scenario's summary tocarryover.mdat the story root, each with aFrom: scenario N (slug)backreference. Tasks have no carryover. - Report -- list each file touched and each entry appended (or "nothing to record"), then tell the user it is safe to
/clear.
File Layout
| Work item | Summary file | Carryover |
|---|---|---|
| Story scenario | ProductSpecification/stories/NN-story-name/summaries/{scenario-slug}.md |
ProductSpecification/stories/NN-story-name/carryover.md |
| Task | ProductSpecification/tasks/N-type-slug/summary.md |
none |
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.
- 2mo ago First seen · 38 lines · 80 tokens per session scan A 29c1cf772fc3
handoff is a skill published in the GitHub repository rakovi4/continue-framework (54 stars, last pushed 29d ago), licensed MIT. It adds 80 tokens to every session and 846 once invoked, about $0.0003 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 skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…