Borrowing it
Nothing to install: this file belongs to moberghr/mtk-agent-toolkit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/moberghr/mtk-agent-toolkit/main/.claude/skills/handoff/SKILL.mdgit clone --depth 1 https://github.com/moberghr/mtk-agent-toolkitWrote 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/moberghr/mtk-agent-toolkit/handoff)<a href="https://agentmods.dev/skills/moberghr/mtk-agent-toolkit/handoff"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/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/moberghr/mtk-agent-toolkit/handoff"><img src="https://agentmods.dev/badge/skills/moberghr/mtk-agent-toolkit/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 135 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00039 | $0.00755 |
| Opus 5.5 | $0.00016 | $0.00302 |
| Sonnet 5.5 | $0.00008 | $0.00151 |
| Haiku 4.5 | $0.00004 | $0.00076 |
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 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Overview
A pointer for the next reader, not a transcript. Compaction, the session-start re-injection of tasks/todo.md and recent handoffs, and the workflow artifact already carry your own session forward; write a handoff when a teammate (or a fresh session tomorrow) must pick up unfinished work.
When To Use
- Handing work to a teammate, or ending a session with non-trivial uncommitted work
- The engineer asks to "save state" or "hand off" — not when everything is committed with a clear message
Workflow
Resolve the helpers once (project-local first, then the plugin root):
res() { [ -n "${MTK_HELPER_ROOT:-}" ] && echo "$MTK_HELPER_ROOT/scripts/$1" || ([ -f "scripts/$1" ] && echo "scripts/$1" || echo "${CLAUDE_PLUGIN_ROOT}/scripts/$1"); }
WFA="$(res workflow-artifact.sh)"; HS="$(res handoff-state.sh)"
Resume mode first. If the request is to continue / resume / pick up, or /mtk handoff arrives while bash "$HS" list --open --branch "$(git branch --show-current)" shows an open note and the engineer did not ask to save state: do not write a note (three sessions regenerated one instead of resuming).
bash "$WFA" resume "$(bash "$HS" field <note> workflow)"— online, so PR drift is checked. Read the note.bash "$HS" accept <note>(expirefor an obsolete note). If a helper is missing or exits non-zero, say the note's state was not updated.- Continue from
next_command; the user's latest message wins over the note.
Write mode. The script renders the whole note (frontmatter, git facts, PRs/CI, units, traps); you supply only the next step, decisions and open questions.
- Active workflow:
bash "$WFA" checkpoint "$MTK_WF_UUID" --next "<what the next session does first>" --decision "<decision — one-line reason>"… [--needs-user "<question> | default: <default>"]. No active workflow:MTK_WF_UUID=$(bash "$WFA" init TASK --goal "<goal>"), then checkpoint. - Exit 3 means
--nextnames a finished unit: fix the text and re-run (nothing was written). - Notes are git-ignored via
docs/handoffs/.gitignore, created by the script; they expire after 14 days. - Update the workflow's Claude Artifact per
.claude/references/artifact-publishing.md(no-op when unavailable orMTK_ARTIFACT_PUBLISH=0; disk first). - Tell the engineer the note path and any artifact URL: "after /clear, type anything — the next session is offered this checkpoint".
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 Changed · -13 lines bbdb8b4d3484
- 13d ago Changed · +15 lines 65e90ae8d521
- 16d ago Changed · -108 lines · -3 tokens per session f643594a92f3
- 1mo ago Changed 1d8533c746e9
- 2mo ago First seen · 152 lines · 42 tokens per session scan A 87b162c10f9b
handoff is a skill published in the GitHub repository moberghr/mtk-agent-toolkit (9 stars, last pushed 8d ago), licensed MIT. It adds 39 tokens to every session and 755 once invoked, about $0.0002 per session on Opus 5.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
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, source notes, and cross-links; also learn durable lessons from a set of conversations, transcripts, or past sessions (/learn), including the Learn from conversations and Learn from Memory…
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
forget
Remove a personal fact, preference, relationship detail, topic, or prior event from Muse's active memory and stop existing copies or automations from bringing it back. Use for explicit requests such as 'forget that', 'don't remember this about me', or 'remove that from your memory'. Do not use when 'forget it' merely…
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…