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 skills/jtsternberg/claude-plugins/handoffnpx skills add jtsternberg/claude-plugins --skill 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/handoff)<a href="https://agentmods.dev/skills/jtsternberg/claude-plugins/handoff"><img src="https://agentmods.dev/badge/skills/jtsternberg/claude-plugins/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.00042 | $0.00909 |
| Opus 5 | $0.00021 | $0.00454 |
| Sonnet 5 | $0.00008 | $0.00182 |
| Haiku 4.5 | $0.00004 | $0.00091 |
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 5d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Bank the current work's context so a fresh agent can continue it. Handoffs live in one of two backends — a beads issue when beads is available, a HANDOFF*.md file otherwise.
Backend preflight
command -v bd >/dev/null 2>&1 && [ -d .beads ] && echo "Backend: beads — read references/beads.md before writing" || echo "Backend: files — read references/files.md before writing"
If the preflight above didn't run, run the check yourself: command -v bd >/dev/null 2>&1 && [ -d .beads ] → beads. Read exactly one reference (references/beads.md or references/files.md) for where and how the handoff is stored, then fill the contract below.
Work name (both backends)
Name the handoff for the work, not just the branch. Default to git branch --show-current; when that doesn't describe the work — a generic default branch (main, master, develop, trunk), a bare ticket ID, or a branch carrying several unrelated tasks — pick a short kebab-case name from what this session is actually about (e.g. grafana-skill). Not in a git repo / detached HEAD with no obvious short name → no name.
Content contract (both backends)
Sections, in order:
-
Goal — what we're trying to accomplish. If it evolved from the original ask, note how and why.
-
Current Progress — what's been done so far.
-
Files Changed — files modified, created, or deleted this session.
-
What Worked — approaches that succeeded.
-
What Didn't Work — approaches that failed, so they're not repeated.
-
Next Steps — concrete, ordered action items for continuing.
-
Anchor — omit when not in a git repo. Exact shape (the
HEAD:line is machine-parsed for drift detection):## Anchor - Branch: <git branch --show-current> - HEAD: `<git rev-parse HEAD>` - Written: <date -u +%Y-%m-%dT%H:%M:%SZ> -
Session — run:
# Codex: this path resolves under Claude Code; substitute the directory containing this SKILL.md. SKILL_DIR="${CLAUDE_SKILL_DIR}" bash "$SKILL_DIR/scripts/session-info.sh"
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 78 lines · 42 tokens per session scan A e32d0d90b5fc
handoff is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed today), licensed MIT. It adds 42 tokens to every session and 909 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.