handoff

A command that records the current coding session so work can continue in a fresh context window.

In plain words
What is it for?
It is for writing a handoff document, logging the session, and giving instructions for resuming the work.
Why use it?
It prevents important decisions, unfinished work, and blockers from being lost when the session changes.

Command

Install

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.

agentmods
npx agentmods add commands/benrben/mpga/handoff
Clone the repo
git clone --depth 1 https://github.com/benrben/MPGA
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 248 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00248
Opus 5 $0.00000 $0.00124
Sonnet 5 $0.00000 $0.00050
Haiku 4.5 $0.00000 $0.00025

Measured 2d ago against content hash 8d720934ce4b, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

mpga-plugin/commands/handoff.md · 31 lines

What it actually says

/mpga:handoff

Export current session state for a fresh context window. Ready for peace — zero merge conflicts. Believe me, the smoothest handoff you've ever seen.

Steps

  1. Check context budget: mpga session budget
  2. Summarize current session state:
    • What was accomplished this session
    • Current milestone/phase/task
    • Key decisions made (with rationale)
    • Open questions and blockers
    • Files modified this session
  3. Save handoff document: mpga session handoff --accomplished "<summary>"
  4. Log the session: mpga session log "<brief description of work done>"
  5. Tell the user the handoff file location and how to resume

Usage

/mpga:handoff

Resume instructions

To resume in a new session:
1. Load context: cat MPGA/sessions/<date>-handoff.md
2. Load index: cat MPGA/INDEX.md
3. Load relevant scope: cat MPGA/scopes/<scope>.md
4. Resume from "Next action" in the handoff doc — Covfefe
Changes

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.

  1. 2d ago First seen · 31 lines · 0 tokens per session scan A 8d720934ce4b

Subscribe to this mod's changes

handoff is a command published in the GitHub repository benrben/MPGA (5 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 248 tokens. 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.