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 giltotherescue/velocity-agent-skills --skill vl-handoffgit clone --depth 1 https://github.com/giltotherescue/velocity-agent-skillsWrote 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/giltotherescue/velocity-agent-skills/vl-handoff)<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.
<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>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 | $0.00055 | $0.00577 |
| Sonnet 5 | $0.00022 | $0.00231 |
| Haiku 4.5 | $0.00011 | $0.00115 |
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 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 — 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 --shortgit 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.
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 · 153 lines · 109 tokens per session scan A ef44552ee910
vl-handoff is a skill published in the GitHub repository giltotherescue/velocity-agent-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 109 tokens to every session and 1,154 once invoked, about $0.0005 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
to-goal
Turn an approved spec, agent-ready ticket, tracker frontier, or partially implemented ticket into a verifiable execution goal without re-interviewing the user. Use after to-tickets or triage, before starting a fresh implementation session; use --all only for an explicitly requested cross-ticket goal.
handing-off-work
Hands off unfinished work with a closed-loop briefing of state, changed conditions, remaining scope, authority limits, and open evidence. Use when AI-agent, reviewer, verifier, releaser, or resumed-thread work transfers to a new owner. Do not use when the same owner continues uninterrupted with full context.
tracking-deficiencies
Keeps a standing register of known deficiencies so flaky tests, noisy alerts, unowned services, and recurring incidents get aged, owned, and fixed or formally risk-accepted instead of quietly normalized. Use when a known problem will outlive a single change. Do not use for a one-off lesson already closed inside a…
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
trellis-workflow-enhancer
Audit and apply real, project-local Trellis integrations for Matt Pocock and Waza skills, with phase routing, hook injection, durable artifact handoffs, and smoke-test evidence. Use when a user wants to strengthen, compare, modernize, integrate, or debug Trellis with Matt/Waza workflows, especially when skills are…
specgate-work-preparation
Use when preparing a request or existing source documents for SpecGate approval, creating quick SpecGate work, publishing an artifact version, or repairing artifact readiness before implementation.