Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add superfly/claude-plugins/plugin install sprite-handoffWrote 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/commands/superfly/claude-plugins/handoff)<a href="https://agentmods.dev/commands/superfly/claude-plugins/handoff"><img src="https://agentmods.dev/badge/commands/superfly/claude-plugins/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/commands/superfly/claude-plugins/handoff"><img src="https://agentmods.dev/badge/commands/superfly/claude-plugins/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.00015 | $0.01027 |
| Opus 5.5 | $0.00006 | $0.00411 |
| Sonnet 5.5 | $0.00003 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00103 |
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 1mo 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hand Off to Remote Claude Code
Transfer the current work to a Claude Code instance running on a sprite in the cloud. This enables background processing, parallel work, or offloading long-running tasks.
Workflow
-
Ensure sprite is ready
- Check for active sprite with
sprite use - If none, create one or ask user to run
/sprite:create
- Check for active sprite with
-
Generate handoff context
- Create a summary of the current conversation/task
- Combine with user's task description
- Format as a prompt for the remote Claude
-
Run the handoff using the CLI tool
$CLAUDE_PLUGIN_ROOT/bin/sprite-handoff run <sprite-name> "<prompt>" [flags]The
runcommand handles everything:- Creates git worktree for session isolation
- Syncs all git-tracked files
- Creates initial commit
- Retrieves Claude OAuth token
- Launches Claude Code on the sprite
Available flags:
--model <model>- Specify model (sonnet, opus, haiku)--max-budget <amount>- Set spending limit in USD--source <dir>- Source directory (default: current dir)-v- Verbose output
-
Return session info
- The command outputs the session ID
- Explain how to resume:
sprite-handoff run <sprite> "<prompt>" --resume <session-id> - Explain how to pull changes:
sprite-handoff pull <session-id>
Handoff Prompt Format
The prompt passed to the run command should include context:
## Context
[Summary of conversation and what was being worked on]
## Project State
[Key files, recent changes, current status]
## Task
[User's task description - what to continue working on]
## IMPORTANT: Commit Your Changes
You MUST commit all changes before finishing. The user will pull your work
using `git diff`, so uncommitted changes will be lost.
When done, run:
git add -A && git commit -m "Description of changes"
## Instructions
- Work autonomously on this task
- Commit all changes with a descriptive message when complete
- Write a summary of what was done to HANDOFF_RESULT.md
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.
- 1mo ago First seen · 139 lines · 15 tokens per session scan A 317a0b1689bf
handoff is a command published in the GitHub repository superfly/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 15 tokens to every session and 1,027 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.