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/dixus/claudeframework/handoffnpx skills add dixus/claudeframework --skill handoffgit clone --depth 1 https://github.com/dixus/claudeframeworkWhat 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.00032 | $0.00472 |
| Opus 5 | $0.00016 | $0.00236 |
| Sonnet 5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 3d 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.
What it actually says
Capture the current session state into a timestamped handoff file.
$ARGUMENTS is optional — pass a short label to identify the handoff (e.g. scoring-engine-wip).
Goal
Write a concise handoff file that lets a fresh session resume exactly where this one left off — without needing to re-read the conversation history.
Steps
- Run
git statusandgit diff HEAD --statto see what files changed this session - Check
.claude/specs/for the most recently modified spec (the active work item) - Check
.claude/reviews/for any open review reports - Identify the current pipeline position:
- Speccing → implementing → reviewing → fixing → testing → done
- Write
.claude/handoffs/YYYY-MM-DD-HH-MM.mdusing this structure:
# Handoff: <label or inferred task name>
Date: <timestamp>
## Current task
<One sentence: what are we building or fixing?>
## Pipeline position
<Which skill was running or is next: /0_spec / /1_implement / /2_review / /3_fix / /4_test>
## Active files
- Spec: `.claude/specs/<name>.md` (if applicable)
- Review: `.claude/reviews/<name>-review.md` (if applicable)
- Key source files: <list only files actively being worked on>
## Decisions made this session
<Bullet list of non-obvious choices made — things not visible from reading the code>
## Open questions
<Unresolved issues or things to verify before continuing. Write "None" if clean.>
## Next step
<Exact action to take when resuming — specific enough to execute without rereading the conversation>
- Report the handoff file path
- Remind the user: run
/clearafter confirming the handoff looks correct, then/continuein the new session to restore context
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.
- 3d ago First seen · 52 lines · 32 tokens per session scan A d7bc1a285988
handoff is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 32 tokens to every session and 472 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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
lark-im
飞书即时通讯：收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片（Interactive Card）、监听卡片按钮回调（card.action.trigger）。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶（添加/移除/查询置顶会话）、管理标签数据、处理卡片回调时使用。.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
reflect
Review recent work, find repeated workflow patterns, and suggest reusable skills, agents, commands, config changes, or playbooks. Use when the user asks to learn from past sessions, improve recurring workflows, or identify what should be turned into reusable agent instructions.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
organize-threads
猫猫辅助整理未分类 thread，分析标题和元数据，建议合适的标签。 Use when: 用户说"帮我整理"、"分类 thread"、点击整理按钮。 Not for: 删除/编辑标签本身。 Output: 按 thread 的标签建议列表。.