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 d-gangz/dgang-skills --skill handoffgit clone --depth 1 https://github.com/d-gangz/dgang-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/d-gangz/dgang-skills/handoff)<a href="https://agentmods.dev/skills/d-gangz/dgang-skills/handoff"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-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/d-gangz/dgang-skills/handoff"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-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.00039 | $0.00515 |
| Opus 5 | $0.00019 | $0.00258 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00052 |
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 12d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pass the baton for a unit of work between two user-visible sessions, so each session's context stays focused on its own job. A side session takes on delegated work without bloating the origin's context; when it finishes, results flow back. For the return trip to land, whoever hands off must leave an address the other session can find — the mechanics below hinge on this.
Two directions
Send off — delegate to a new side session:
- Compose the brief (below).
- Spin off the side session and pass it the brief, using your harness mechanics. Open it in the same project as the origin by default; target a different project only when the user asks for one.
Hand back — return results to the session that spawned you:
- Compose the brief (below), covering what you did and what you produced.
- Resolve the origin session and deliver the brief to it, using your harness mechanics.
The brief
Carry the brief inline in the spin-off / hand-back message, written so the receiving session can continue with no other context. If the user passed arguments, treat them as a description of what the receiving session should focus on and tailor the brief accordingly.
- Summarise the work: goal, what's done, what's left, key decisions.
- Include a suggested skills section naming skills the receiving session should invoke.
- Reference existing artifacts (specs, plans, ADRs, issues, commits, diffs) by path or URL — do not restate their content.
- Redact secrets and PII (API keys, passwords, personal data).
- On a send off, include the origin's return address so the side session can hand back (see harness mechanics).
Only when the context is too large to carry inline, write it to the OS temp directory (not the workspace) and include the file path as a pointer in the message.
Harness mechanics
Spin-off and addressing differ by harness. Read the file for the one you are running in:
- Claude Code →
references/claude-code.md - Codex →
references/codex.md
What ships with it
3 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.
- 12d ago First seen · 38 lines · 39 tokens per session scan A 31ecbd234a0d
handoff is a skill published in the GitHub repository d-gangz/dgang-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 515 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…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
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.