pickup

A command for continuing work from a saved handoff snapshot. A handoff is a short written summary of the current task, rather than a complete conversation history.

In plain words
What is it for?
Finding a handoff by file, thread name, or discovery order, listing active handoffs, and continuing a task from the selected snapshot.
Why use it?
It lets another session pick up ongoing work while checking the saved information against the current files and state.

Command

Part of the session-continuity plugin — 2 commands shipped together

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/cwakim/claude-plugins/pickup
Clone the repo
git clone --depth 1 https://github.com/cwakim/claude-plugins

Or install session-continuity, the plugin that ships this one along with the rest of its 2 commands.

Per session 26 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,545 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.00026 $0.01545
Opus 5 $0.00013 $0.00772
Sonnet 5 $0.00005 $0.00309
Haiku 4.5 $0.00003 $0.00154

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

Security

Grade A, and why

pickup 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.

plugins/session-continuity/commands/pickup.md · 60 lines

How it starts

The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Pickup

Read a handoff snapshot written by /handoff and continue the work (or the conversation) from it.

This is the other half of /handoff: a baton pass, not a session restore. It deliberately reads a distilled summary rather than replaying a transcript. (Named pickup, not resume, to avoid colliding with Claude Code's built-in /resume.)

Arguments ($ARGUMENTS)

  • A path (anything containing / or ending in .md) → read that file. Expand a leading ~.
  • The word list → don't pick anything up; show what's in flight instead. Follow the List mode section below.
  • Any other text → treat it as a thread name: match it (case-insensitively, allowing partial matches) against the titles and goals in ~/.claude/handoff-index.md. One live match → pick that up. Several → show them and ask. None → say so and fall back to the discovery order below.
  • No argument → find the handoff via the discovery order below.

Discovery order (no argument given)

A handoff does not always live in the current repo: it may have been written from a sibling repo, the Desktop, or elsewhere. Walk this order and stop at the first hit:

  1. .claude/handoff.md in the current working directory.
  2. The newest live entry in ~/.claude/handoff-index.md (the pointer index /handoff maintains). Read the index and walk it top-down to the first path that still exists: entries can point at handoffs that were since deleted, so do not dead-end on a stale newest entry. Prune as you go: any entry whose path no longer exists is dead, so rewrite the index without those lines (keep the live ones in order) and tell the user which you removed. This keeps the index from accumulating pointers to deleted handoffs.
  3. If neither resolves, say so and ask where the handoff lives.

If the resolved handoff lives outside the current working directory, say so explicitly and name its absolute path before acting on it, so a stale or wrong-repo pickup is obvious rather than silent.

Read the full file on GitHub · 60 lines

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 · 60 lines · 0 tokens per session scan A 780a4f42fc1c

Subscribe to this mod's changes

pickup is a command published in the GitHub repository cwakim/claude-plugins (2 stars, last pushed 12d ago), licensed MIT. It adds 26 tokens to every session and 1,545 once invoked, about $0.0001 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.