Borrowing it
Nothing to install: this file belongs to rjwalters/kicad-tools. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/rjwalters/kicad-tools/main/.claude/commands/repo/handoff.mdgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/rjwalters/kicad-tools/handoff)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/handoff"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/handoff.svg" alt="Measured on agentmods" 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.00034 | $0.01580 |
| Opus 5 | $0.00017 | $0.00790 |
| Sonnet 5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
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 6d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo:handoff — Roll the Session Safely
Rolling a Claude Code session — quitting the CLI and starting fresh — is the moment a session's most valuable output is most likely to be lost, because what is worth carrying forward is exactly what exists only in the session's context: in-flight state, settled decisions, and empirically-discovered traps. This command makes the roll a repeatable ritual instead of an ad-hoc scramble.
It composes the existing commands rather than reimplementing them — [[followups]] to capture deferred work, [[reset]] to reach a clean git baseline — and adds only what does not exist yet: the CLI version check, the handoff note, and exact restart instructions.
Relationship to /compact: compaction handles the soft boundary —
context pressure within a continuous session. /repo:handoff handles the
hard boundary: process restart, CLI upgrade, or a deliberate fresh start. If
the version check below finds no update and the only pressure is context size,
say so — a /compact may be all that's needed.
Usage
/repo:handoff # Run the ritual end-to-end, confirmations as usual
/repo:handoff --dry-run # Preview the note and proposed actions; file, prune, and write nothing
/repo:handoff --prune # Pass --prune through to the reset stage
Steps — ordering is load-bearing
Run the stages in exactly this order. Each later stage depends on the earlier ones having actually happened.
1. File follow-ups first (see [[followups]])
Run the full [[followups]] flow — mine the session, propose, confirm, file. This must precede reset because [[reset]] prunes branches, worktrees, and stashes that a follow-up may need to reference, and filing wants the git state reset is about to remove. Record the issue URLs actually filed (and anything proposed-but-declined) — the note needs them.
Under --dry-run, run followups in its own --dry-run mode: propose, file
nothing.
2. Reset to baseline (see [[reset]])
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.
- 6d ago First seen · 150 lines · 34 tokens per session scan A 85abde2338cf
handoff is a command published in the GitHub repository rjwalters/kicad-tools (56 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,580 once invoked, about $0.0002 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
status
Show the Salesforce project banner — connected org, edition, API, project metadata stats, and MCP server status.
setup
Verify ClauDex prerequisites — Codex CLI, authentication, and git.
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
instinct-import
Import a portable YAML instinct pack with confidence-gated merge (Instinct Engine).
acos-checkpoint
Create checkpoints before risky operations. Rollback if things go wrong.
release-notes
从 git 历史生成发布说明——维护 Keep a Changelog 风格的 CHANGELOG.md 条目并产出面向用户的发布正文，不决定版本号、不改动 git 状态.