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/dsifry/metaswarm/handoffnpx skills add dsifry/metaswarm --skill handoffgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/handoff)<a href="https://agentmods.dev/skills/dsifry/metaswarm/handoff"><img src="https://agentmods.dev/badge/skills/dsifry/metaswarm/handoff.svg" alt="Measured on agentmods" 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.00040 | $0.02188 |
| Opus 5 | $0.00020 | $0.01094 |
| Sonnet 5 | $0.00008 | $0.00438 |
| Haiku 4.5 | $0.00004 | $0.00219 |
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 6d 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 — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Skill
Capture everything a fresh agent with zero prior context needs to resume the current work, write it to a single self-contained markdown document, and hand it off with one unambiguous sentence:
Read
docs/handoffs/<file>.mdand do<the next concrete action>.
Use this when a session is ending, when context is about to be compacted, when you are switching machines or sessions, or when the user explicitly asks for a handoff. The goal is zero context loss: the receiving agent should be able to act correctly after reading exactly one file.
Output Contract
This skill produces exactly two things:
-
A handoff document at
docs/handoffs/handoff-<YYYY-MM-DD-HHmm>.md(created if the directory does not exist). It is comprehensive, self-contained, and links to — or quotes — every artifact the next agent must read. -
A single closing sentence, and nothing else after the document is written, of the exact form:
Read docs/handoffs/handoff-2026-06-17-1432.md and do <YYY>.Where
<YYY>is one concrete, actionable next step (an imperative, not a vague theme). Good: "implement theparseConfigvalidation insrc/config.ts:84and maketests/config.test.tspass". Bad: "continue the work" / "look into the config stuff".
The sentence is the deliverable the user hands to the next agent. The document is what makes that sentence safe to follow.
Method
Step 1 — Reconstruct what we are working on
Review the session to date and answer, concretely:
- Objective: What is the user actually trying to accomplish? State it in one or two sentences.
- Definition of Done: What does "finished" look like? Enumerate verifiable acceptance criteria if any exist.
- Why: The motivation/problem behind the task, so the next agent does not re-litigate settled decisions.
Pull from: the user's original request, any GitHub Issue (gh issue view <n>), the design/plan docs, and the arc of the conversation.
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.
- 6d ago First seen · 204 lines · 40 tokens per session scan A 8d696f1ee2ea
handoff is a skill published in the GitHub repository dsifry/metaswarm (409 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 2,188 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-30.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
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…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
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…