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 psenger/ai-agent-skills --skill handoffgit clone --depth 1 https://github.com/psenger/ai-agent-skillsWrote 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/psenger/ai-agent-skills/handoff)<a href="https://agentmods.dev/skills/psenger/ai-agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/psenger/ai-agent-skills/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/psenger/ai-agent-skills/handoff"><img src="https://agentmods.dev/badge/skills/psenger/ai-agent-skills/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.00194 | $0.00896 |
| Opus 5 | $0.00097 | $0.00448 |
| Sonnet 5 | $0.00039 | $0.00179 |
| Haiku 4.5 | $0.00019 | $0.00090 |
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 10d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Saves or loads a structured JSON snapshot of session state. Use the schema in references/schema.md for all fields.
Mode Selection
- User wants to save / pause / context is full → CREATE workflow
- User wants to resume / load / continue → RESUME workflow
- After 5+ file edits or a major decision → suggest: "We've made good progress — say 'create handoff' when you're ready to save state and start fresh."
CREATE Workflow
Step 1 — Determine Output File
Use the user's argument if provided (e.g. /handoff auth-work.json). Otherwise default
to .claude/handoffs/YYYY-MM-DD-HHMMSS-<slug>.json in the project root, where <slug>
is 2–4 words from the task goal (e.g. auth-refactor, payment-api). Create
.claude/handoffs/ if it doesn't exist.
Step 2 — Analyse the Session
Review the full conversation and all modified files, then extract:
- The primary goal and what "done" looks like (acceptance criteria)
- All architectural and design decisions reached, with rationale
- What has been completed and can be verified
- What still needs to be done, in priority order
- Hard constraints and non-negotiables
- Known bugs, issues, or unresolved warnings
- Which files were changed and what was done to each
Step 3 — Write the Handoff File
Write the JSON using the schema in references/schema.md. Do not omit any top-level
field — use [] if there is nothing to report.
Step 4 — Confirm and Guide the User
Handoff written to: <filename>
Summary:
- Task: <goal>
- Completed: <N> steps
- Pending: <N> steps
- Constraints: <N>
- Open issues: <N>
- Modified files: <N>
Next steps:
1. Run /clear to wipe the context window
2. Start a new session
3. Paste this prompt to resume:
"<resume_prompt value>"
Do not run
/clearyourself — the user must do this manually.
RESUME Workflow
Step 1 — Locate the File
Use the user's argument if given. Otherwise read .claude/handoffs/ and pick the most
recent file by filename timestamp. If the directory is empty or missing, tell the user.
What ships with it
13 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.
- .skillignore 11 B
- .workspace/evals/evals.json 5.0 KB
- .workspace/evals/files/handoff-fixture.json 4.4 KB
- .workspace/evals/iteration-1/eval-1/with_skill/outputs/.claude/handoffs/2026-04-25-120000-express-jwt-api.json 3.4 KB
- .workspace/evals/iteration-1/eval-1/with_skill/outputs/output.txt 899 B
- .workspace/evals/iteration-1/eval-1/without_skill/outputs/output.txt 2.6 KB
- .workspace/evals/iteration-1/eval-2/with_skill/outputs/db-schema-work.json 4.7 KB
- .workspace/evals/iteration-1/eval-2/with_skill/outputs/output.txt 915 B
- .workspace/evals/iteration-1/eval-2/without_skill/outputs/output.txt 4.0 KB
- .workspace/evals/iteration-1/eval-3/with_skill/outputs/output.txt 7.1 KB
- .workspace/evals/iteration-1/eval-3/without_skill/outputs/output.txt 4.5 KB
- .workspace/evals/trigger-evals.json 3.5 KB
- references/schema.md 5.0 KB
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.
- 10d ago First seen · 115 lines · 194 tokens per session scan A 21ee917e7642
handoff is a skill published in the GitHub repository psenger/ai-agent-skills (10 stars, last pushed 3mo ago), licensed MIT. It adds 194 tokens to every session and 896 once invoked, about $0.0010 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
neat-freak
Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and…
mnemos
Task-scoped memory lifecycle — typed MnemoGraph prevents lossy context compaction by treating facts/decisions/code-refs/handoffs as distinct node types with per-type eviction policies.
grimoire
Use when the user says 'update context', 'update claude', 'save library', or after significant project changes.
ln-31-performance-optimizer
Profiles and improves a measured latency, throughput, CPU, memory, or I/O problem. Not for speculative tuning or cosmetic refactoring.
keep-the-why
Extract and preserve the reasoning code cannot explain - decisions, rejected alternatives, workarounds, incidents, constraints - plus project setup and maintainer interviews. Not for what changed (see Keep a Changelog) - only why.