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 agentmods add commands/restarter/lets-workflow/review-handoffgit clone --depth 1 https://github.com/restarter/lets-workflowWhat 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 | $0.00061 | $0.03212 |
| Opus 5 | $0.00030 | $0.01606 |
| Sonnet 5 | $0.00012 | $0.00642 |
| Haiku 4.5 | $0.00006 | $0.00321 |
Grade A, and why
review-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 3d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Handoff - Brief for an External Reviewer
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 - do not review anything yourself, do not edit any file
- 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:review-handoff # infer the target from context; asks only if genuinely ambiguous
/lets:review-handoff <PR-url-or-number> # GitHub or Bitbucket PR
/lets:review-handoff --pr <id-or-url> # alias of the bare form above
/lets:review-handoff --local # uncommitted changes
/lets:review-handoff --staged # staged changes only
/lets:review-handoff --last-commit # last commit
/lets:review-handoff --branch # full branch vs the merge branch (three-dot, like a PR)
/lets:review-handoff --plan # newest plan in .lets/plans/
/lets:review-handoff --plan <path> # a specific plan file
/lets:review-handoff --file <path> # one file
/lets:review-handoff --commits <N> # handoff-only: the last N commits (a fix round)
/lets:review-handoff --range <a>..<b> # handoff-only: an explicit range
/lets:review-handoff --spec <path> # what the reviewer judges against (or a bare task id)
/lets:review-handoff --spec none # deliberately no spec - no spec line, no caveat
Selectors match /lets:review, with two deliberate differences: --commits / --range are handoff-only (review has no target for "the commits that answer a review round"), and --pr is kept as an alias because it is the spelling this tool shipped with. Review's output modifiers --json and --workflow are not implemented here.
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.
- 3d ago First seen · 142 lines · 61 tokens per session scan A abf582242875
review-handoff is a command published in the GitHub repository restarter/lets-workflow (17 stars, last pushed 10d ago), licensed MIT. It adds 61 tokens to every session and 3,212 once invoked, about $0.0003 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.