handoff

handoff is a command for Claude Code from realmpastai-web/claude-design-suite. It costs 10 tokens per session (199 once invoked), scanned A, original, MIT.

A command for preparing a developer handoff, the package of design details needed to build a design accurately. It includes measurements, interaction behavior, assets, quality checks, and implementation notes.

In plain words
What is it for?
Use it to document visual specifications, interaction states, assets, QA checks, design review results, and the version being handed over.
Why use it?
It gathers scattered design decisions into one package for the development team. This reduces uncertainty about how screens should look and behave.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the design-ops plugin — 7 skills, 3 commands shipped together

Good fit Use it to document visual specifications, interaction states, assets, QA checks, design review results, and the version being handed over.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/realmpastai-web/claude-design-suite/handoff
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.

Clone the repo
git clone --depth 1 https://github.com/realmpastai-web/claude-design-suite

Made for: Claude Code.

Or install design-ops, the plugin that ships this one along with the rest of its 7 skills, 3 commands.

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.

agentmods badge for handoff

README.md
[![agentmods](https://agentmods.dev/badge/commands/realmpastai-web/claude-design-suite/handoff/github.svg)](https://agentmods.dev/commands/realmpastai-web/claude-design-suite/handoff)
Your own site
<a href="https://agentmods.dev/commands/realmpastai-web/claude-design-suite/handoff"><img src="https://agentmods.dev/badge/commands/realmpastai-web/claude-design-suite/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.

agentmods 80×15 button for handoff

Your own site · 80×15
<a href="https://agentmods.dev/commands/realmpastai-web/claude-design-suite/handoff"><img src="https://agentmods.dev/badge/commands/realmpastai-web/claude-design-suite/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 199 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00010 $0.00199
Opus 5 $0.00005 $0.00100
Sonnet 5 $0.00002 $0.00040
Haiku 4.5 $0.00001 $0.00020

Measured 9d ago against content hash e68b16af5514, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

plugins/design-ops/commands/handoff.md · 17 lines

What it actually says

/handoff

Generate a developer handoff package.

Steps

  1. Visual specs — Document all measurements and tokens using handoff-spec skill.
  2. Interaction specs — Define states and behaviors using handoff-spec skill.
  3. QA criteria — Create implementation checklist using design-qa-checklist skill.
  4. Review readiness — Verify against review criteria using design-review-process skill.
  5. Version — Tag the design version being handed off using version-control-strategy skill.
  6. Package — Compile all specs, assets, and notes.

Output

Complete handoff package with visual specs, interaction specs, asset list, QA checklist, and implementation notes. Consider following up with /setup-workflow to establish the ongoing QA process.

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.

  1. 9d ago First seen · 17 lines · 10 tokens per session scan A e68b16af5514

Subscribe to this mod's changes

handoff is a command published in the GitHub repository realmpastai-web/claude-design-suite (2 stars, last pushed 4mo ago), licensed MIT. It adds 10 tokens to every session and 199 once invoked, about $0.0001 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.