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 skills add jtsternberg/claude-plugins --skill pickup-handoffgit clone --depth 1 https://github.com/jtsternberg/claude-pluginsWrote 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/skills/jtsternberg/claude-plugins/pickup-handoff)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/pickup-handoff"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/pickup-handoff/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/pickup-handoff"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/pickup-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01147 |
| Opus 5 | $0.00022 | $0.00574 |
| Sonnet 5 | $0.00009 | $0.00229 |
| Haiku 4.5 | $0.00004 | $0.00115 |
Grade A, and why
pickup-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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pickup Handoff
Resume work from a handoff written by a previous agent. The companion handoff skill generates the correct pickup invocation for the active harness.
Assume the user has NOT read the handoff. They are handing you a pointer and expecting you to get up to speed and tell them what's going on. Don't silently continue — surface your understanding and plan first.
The handoff is a boot artifact, not a living document. Read it once, boot from it, then work from the repo — the repo is the source of truth from that moment on. Never update a handoff after reading it:
- Don't append progress to it.
- Don't "keep it current" as you work.
- Don't edit it "for the next agent" — writing a fresh handoff at session end is the
handoffskill's job, not an edit to this one.
Steps
-
Find the handoff.
If
$ARGUMENTSholds an identifier, that IS the handoff — go straight to step 2. Thehandoffskill emits it precisely so this step costs one command:- looks like a beads id (e.g.
myproject-20xu) →bd show <id> - looks like a path →
Readit
Do not also glob for
HANDOFF*.md, list openpending-handoff:issues, or check the branch — you were told which one. Skip all of it. Only fall through to the search below if the identifier turns out not to resolve, and say so when you do.With no argument, search in this order:
HANDOFF*.mdin the current working directory — in a git repo, prefer the one matching the current branch (git branch --show-current); otherwise fall back toHANDOFF.md.- If bd is available (
command -v bd >/dev/null 2>&1 && [ -d .beads ]): open issues titledpending-handoff:—bd list --status open,in_progress --title-contains "pending-handoff:" --json. - Multiple candidates and no clear match → list them and ask which to use.
- looks like a beads id (e.g.
-
Read it in full (file, or
bd show <id>). -
Reconcile against reality. The doc describes the past; check the present. In a git repo (
git rev-parse --git-dirsucceeds):- If it has an Anchor section, run
git log --oneline <anchor-sha>..HEAD— report "N commits since the handoff was written" and what they touched. - Run
git status; spot-check the doc's "Files Changed" claims. - Note anything the doc claims that the repo contradicts.
- If it has an Anchor section, run
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.
- 8d ago First seen · 62 lines · 43 tokens per session scan A 1e0636b32980
pickup-handoff is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 4d ago), licensed MIT. It adds 43 tokens to every session and 1,147 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…