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/naimkatiman/continuous-improvement/handoffgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/naimkatiman/continuous-improvement/handoff)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/handoff"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/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 | $0.00031 | $0.00515 |
| Opus 5 | $0.00015 | $0.00258 |
| Sonnet 5 | $0.00006 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
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 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.
What it actually says
/handoff
Hand the current session off to a fresh agent by writing a brief, mktemp-backed markdown summary they can pick up cold.
Trigger phrases
/handoff/handoff <what the next session will focus on>- "write a handoff doc"
- "compact this into a handoff"
What happens
- Read the current conversation (and the user's argument, if given) to identify the goal, current state, decisions made, open questions, next concrete step, and skills to load.
- Generate a unique path with
mktemp -t handoff-XXXXXX.mdand read it (it will be empty). - Write the handoff doc to that path. Reference PRDs, plans, ADRs, issues, commits, and diffs by path or URL — do not duplicate their content.
- Suggest the skills the next session should load.
What goes in the doc
A one-screen brief, in this order:
- Goal — one sentence on the outcome the user is steering toward.
- Current state — what is actually true on disk / in the system right now.
- Decisions made this session — only what is not already captured in commits or other artifacts.
- Open questions — blocking choices the next agent needs the user to answer.
- Next concrete step — the single action the next agent should take first.
- Skills to load — names of the skills the next session should activate.
Skill file
Full behavior is defined in skills/handoff.md. The verbatim upstream cold-storage copy lives at third-party/mattpocock-skills/skills/in-progress/handoff/SKILL.md; SHA pin in third-party/MANIFEST.md.
Attribution
Ported from mattpocock/skills in-progress/handoff (MIT, © 2026 Matt Pocock).
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 · 43 lines · 31 tokens per session scan A a3b57c310c8d
handoff is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 515 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-31.
Other commands, from other repositories
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
safe-build
Build the application for development or production.
update
Use when: search results seem noisy, after bulk imports, or for periodic memory/registry maintenance.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
milestone-list
PitWay: List every milestone with a concise one-line status.