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 restarter/lets-workflow/plugin install letsWrote 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/restarter/lets-workflow/handoff)<a href="https://agentmods.dev/commands/restarter/lets-workflow/handoff"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/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/restarter/lets-workflow/handoff"><img src="https://agentmods.dev/badge/commands/restarter/lets-workflow/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.00116 | $0.09435 |
| Opus 5.5 | $0.00046 | $0.03774 |
| Sonnet 5.5 | $0.00023 | $0.01887 |
| Haiku 4.5 | $0.00012 | $0.00944 |
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 15d 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff - Brief for Another Agent
Produce ONE message the user copies into another agent. That agent has NO context: not this conversation, not the task, not even which repo. The brief must be complete on its own.
- The brief is the deliverable - review nothing yourself and edit no file of the repository (
--fixis the one exception);--send/--open/--codexhand it on and bring the report back (Step 7) --executeturns a plan's brief from "review this" into "implement this": the receiving agent writes code and commits, this session still edits nothing (Step 5b)--fixapplies the report's verified fixes in THIS session when nothing needs deciding (7.4, theapply-fixesskill); the user typing it is the write authorization for that run - edits only, never a commit- Target selectors mirror
/lets:review, so the same flag reviews here or hands off there; works in any git repo, with or without LETS
IMPORTANT: If the spec below invokes any deferred tool (e.g.
AskUserQuestion), you MUST load and call it as specified. Never skip the call, never substitute a default answer of your own — the tool invocation is part of the contract. This is critical.
Usage
/lets:handoff # infer the target from context; asks only if genuinely ambiguous
/lets:handoff <PR-url-or-number> # GitHub or Bitbucket PR
/lets:handoff --pr <id-or-url> # alias of the bare form above
/lets:handoff --local # uncommitted changes
/lets:handoff --staged # staged changes only
/lets:handoff --last-commit # last commit
/lets:handoff --branch # full branch vs the merge branch (three-dot, like a PR)
/lets:handoff --plan # newest plan in .lets/plans/
/lets:handoff --plan <path> # a specific plan file
/lets:handoff --file <path> # one file
/lets:handoff --commits <N> # handoff-only: the last N commits (a fix round)
/lets:handoff --range <a>..<b> # handoff-only: an explicit range
/lets:handoff --spec <path> # what the reviewer judges against (or a bare task id)
/lets:handoff --spec none # deliberately no spec - no spec line, no caveat
/lets:handoff --plan --codex # run the brief through Codex headless (read-only), relay + verify its report
/lets:handoff --branch --send # type the brief into an agent tab of this worktree (pick one)
/lets:handoff --branch --send antigravity # ... the Antigravity tab (an agent name, or a fragment of the tab title)
/lets:handoff --plan --open # a new Codex tab (read-only) in this worktree gets the brief
/lets:handoff --execute --send codex # the open Codex tab implements the newest plan of this task
/lets:handoff --execute --plan <path> --send # ... a specific plan; pick the tab
/lets:handoff --branch --codex --fix # ... then apply the verified fixes here when nothing needs deciding
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.
- 15d ago Changed · +22 lines 29754aa69a32
- 19d ago Changed · +2 lines 3396736b63e6
- 20d ago Changed · +2 lines 7fe78e586972
- 23d ago Changed · +7 lines 06b61d86a532
- 26d ago Changed · +121 lines · +19 tokens per session 37045198748b
- 28d ago First seen · 253 lines · 97 tokens per session scan A 7390ae4a202c
handoff is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 116 tokens to every session and 9,435 once invoked, about $0.0005 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-09-19.
Other commands, from other repositories
poc
Before building on an unproven idea, get a timeboxed yes/no answer — start a hypothesis-driven POC that skips 80% of the production pipeline and forces ship/pivot/kill at expiry, then promote a shipped POC through the audits it skipped.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
exception
Signed gate-exception registry — replace ad-hoc --admin / --no-verify bypasses with an auditable, signed, expiring record (who · why · gate · scope · expiry). Create / list / check exceptions.
backlog
The project layer: milestones, epics, and user stories with refusing controllers — spec-seeded, sprint-ready.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.
anchors
List what each requirement tag anchors to (read-only).