Borrowing it
Nothing to install: this file belongs to ljchang/mecha. 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/ljchang/mecha/main/.claude/skills/handoff/SKILL.mdgit clone --depth 1 https://github.com/ljchang/mechaWrote 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/ljchang/mecha/handoff)<a href="https://agentmods.dev/skills/ljchang/mecha/handoff"><img src="https://agentmods.dev/badge/skills/ljchang/mecha/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/ljchang/mecha/handoff"><img src="https://agentmods.dev/badge/skills/ljchang/mecha/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.02420 |
| Opus 5.5 | $0.00030 | $0.00968 |
| Sonnet 5.5 | $0.00015 | $0.00484 |
| Haiku 4.5 | $0.00007 | $0.00242 |
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 1mo 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 — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Closing out a session
docs/HANDOFF.md is the file someone reads before deciding what to build next.
That makes staleness worse than absence: a to-do list that mixes shipped work
with open work sends the reader to re-implement something that already exists,
or to skip something that does not.
This skill keeps that from happening. It takes ten minutes and it is the whole reason the doc split is worth maintaining.
Read docs/README.md first if you are unsure which
document a given piece of writing belongs in — this skill only covers moving
things between HANDOFF and HISTORY.
The one rule
Verify against source, never against a commit message.
A commit that says "add the rules cap" may have added a constant and no gate. A commit that says "wire up X" may have wired half of it. The only evidence that an item shipped is the code that implements it.
Verify at a file:line, but write the citation as a symbol — the
function, type, or constant. A line number in a doc is wrong the moment
another lane lands, and it rots silently: on 2026-08-26 two refs drifted
within the hour, and one of them was itself a repair of an earlier stale
ref. Where a line is genuinely needed, name the commit it was verified
against.
This is not pedantry — it is the specific failure that produced a 1,965-line handoff. Items were struck through when their commit landed, and the ones that were never struck through silently became indistinguishable from the ones that were never built.
Procedure
0. Claim the file before writing it
docs/HANDOFF.md and docs/HISTORY.md are single-writer documents that
every lane accumulates into — announced, never raced. Before editing either:
ls .git/worktrees/*/MERGE_HEAD 2>/dev/null # another lane mid-merge?
Check ListAgents for live peer sessions, say you are about to write the
handoff, and sequence behind whoever already claimed it. Two sessions editing
the same handoff is a conflict in the one file whose job is telling the next
session what happened.
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.
- 1mo ago Changed · +3 lines b53f912c5fcf
- 2mo ago First seen · 224 lines · 75 tokens per session scan A 1a7a618b0126
handoff is a skill published in the GitHub repository ljchang/mecha (7 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 2,420 once invoked, about $0.0003 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.
handoff compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| handoffljchang/mecha | Skill | 7 | today | MIT | A | 75 | Claude Code |
| api-interface-designMohitGoyal09/AgentForge | Skill | 65 | 17d ago | MIT | A | 23 | Claude Code, Codex |
| exploreMohitGoyal09/AgentForge | Skill | 65 | 17d ago | MIT | A | 15 | Claude Code, Codex |
| continuum-tools-mcpshyftlabs/continuum | Skill | 84 | 1mo ago | Apache-2.0 | A | 94 | Claude Code |
| continuum-handoffsshyftlabs/continuum | Skill | 84 | 1mo ago | Apache-2.0 | A | 98 | Claude Code |
| continuum-llm-providersshyftlabs/continuum | Skill | 84 | 1mo ago | Apache-2.0 | A | 105 | Claude Code |
| continuum-testingshyftlabs/continuum | Skill | 84 | 1mo ago | Apache-2.0 | A | 80 | Claude Code |