A handoff-writing guide for passing ongoing work to another developer, agent, reviewer, or team. It records the current status, decisions, changed files, checks, risks, and next steps.

Use it to prepare Slack messages, pull-request notes, issue updates, documents, or prompts for another agent to continue the work.

It prevents the next person from having to reconstruct the work from chat history, code changes, and terminal output.

vl-handoff — Skill for Claude Code and Codex by giltotherescue

Install

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.

Any agent

npx skills add giltotherescue/velocity-agent-skills --skill vl-handoff

Clone the repo

git clone --depth 1 https://github.com/giltotherescue/velocity-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/giltotherescue/velocity-agent-skills/vl-handoff/github.svg)](https://agentmods.dev/skills/giltotherescue/velocity-agent-skills/vl-handoff)

Your own site

<a href="https://agentmods.dev/skills/giltotherescue/velocity-agent-skills/vl-handoff"><img src="https://agentmods.dev/badge/skills/giltotherescue/velocity-agent-skills/vl-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/giltotherescue/velocity-agent-skills/vl-handoff"><img src="https://agentmods.dev/badge/skills/giltotherescue/velocity-agent-skills/vl-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 109 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,154 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00109	$0.01154
Opus 5.5	$0.00044	$0.00462
Sonnet 5.5	$0.00022	$0.00231
Haiku 4.5	$0.00011	$0.00115

Measured 2mo ago against content hash ef44552ee910, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vl-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.

skills/vl-handoff/SKILL.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Velocity Handoff

Create a handoff that lets the next person or agent continue from the current state without reconstructing context from chat history, diffs, terminal output, or guesswork.

Operating Mode

Be efficient. If the recipient or medium is obvious from the user's request, infer it and continue. Ask at most one clarifying question only when the answer materially changes the format or content.

Useful question when needed:

Who is this handoff for, and where will you send it?

If the user does not answer or the context is still unclear, default to a developer-to-developer handoff in Markdown.

Determine Audience And Medium

Identify:

Recipient: another AI agent, senior developer, frontend developer, backend developer, product/design reviewer, QA, manager, client, or general team.
Medium: Slack message, GitHub PR/comment, issue tracker, email/doc, README-style handoff, agent continuation prompt, or internal review note.
Goal: continue implementation, review UI/UX, test a feature, make a go/no-go decision, debug an issue, or understand status.

Shape the output to the medium:

Slack: concise, skimmable, action-oriented, with links/artifacts near the top.
GitHub PR/comment: structured, technical, with files, tests, risks, and review focus.
Issue tracker: status, reproduction/verification steps, acceptance criteria, next owner.
Agent handoff: exact current state, constraints, commands run, commands not run, files changed, next task list.
Non-technical review: plain language, visible behavior, screenshots, review questions, and what feedback is needed.

Gather Context

Use available local context before writing:

git status --short
git diff --stat
Relevant staged/unstaged diffs.
Recent commits if the work was committed.
Test/build/browser commands run and their outcomes.
Local URLs, worktree paths, queue/worker commands, logs, screenshot contact sheets, zip files, demos, or generated artifacts.
Explicit decisions or constraints from the conversation.

Read the full file on GitHub · 153 lines

Changes

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 · 153 lines · 109 tokens per session scan A ef44552ee910

Subscribe to this mod's changes

vl-handoff is a skill published in the GitHub repository giltotherescue/velocity-agent-skills (3 stars, last pushed 5mo ago), licensed MIT. It adds 109 tokens to every session and 1,154 once invoked, about $0.0004 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.

Claude Code Project management agent-skills ai-agents codex coding-agents developer-tools

isaac-humanoid-cloud-control

Run streamed Unitree G1 cloud-navigation demos in Isaac Sim with guarded gantry release. Use for demo, destination, Mission Control, or cleanup requests.

NVIDIA/skills · 39 tokens

mcore-split-pr

Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.

NVIDIA/skills · 25 tokens

machinist

Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.

owainlewis/machinist · 47 tokens

task-decomposer

Produces phased task boards from feature requests: dependency-mapped work items, parallelization flags, risk flags, edge cases, test matrices. Triggers on: "decompose this feature", "task breakdown with dependencies", "phased implementation plan", "work breakdown structure". NOT for discovering which decisions are…

Mathews-Tom/armory · 81 tokens

milestone-runner

Use when asked to "run milestones", "execute EXECUTIONPROMPTS.md", "continue the milestone sequence", "run independent milestones in parallel", "merge the stack", or "reconcile M5" after prior work changes the current design. Not for generating plan files; use plan-prompts. Not for repairing one stack; use stacked-prs.

Mathews-Tom/armory · 76 tokens

project-context-setup

Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage…

Mathews-Tom/armory · 109 tokens