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 stefan-jansen/coding-agent-toolkit --skill handoffgit clone --depth 1 https://github.com/stefan-jansen/coding-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/stefan-jansen/coding-agent-toolkit/handoff)<a href="https://agentmods.dev/skills/stefan-jansen/coding-agent-toolkit/handoff"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-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/stefan-jansen/coding-agent-toolkit/handoff"><img src="https://agentmods.dev/badge/skills/stefan-jansen/coding-agent-toolkit/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.00054 | $0.02747 |
| Opus 5.5 | $0.00022 | $0.01099 |
| Sonnet 5.5 | $0.00011 | $0.00549 |
| Haiku 4.5 | $0.00005 | $0.00275 |
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 4d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
handoff — write a cold-startable transition file
You are running the HANDOFF step of the workflow. Your job is to
freeze the current session's state into a single Markdown file that lives in
the shared .workspace/transitions/ tree so any future session on either
host can resume without re-deriving context.
This step is host-neutral: same contract on Claude and Codex. The shared
.workspace/ directory is the host-swap primitive (see backlog #8) —
there is no "execute as the other host" verb because the durable state is
what makes the swap work, not orchestration.
When to use
- Switching hosts mid-feature (Claude → Codex or vice versa). Neither host can resume the other's session, so the transition file is the only carrier.
- Before a deliberate
/clear, or at a day boundary, when the next session should start from curated state. - After a milestone ships, before starting the next one.
Not before /compact or as the context fills. Both hosts compact
automatically and write their own summary (the transition plugin copies
Claude's to .workspace/transitions/), so a handoff then is a second summary of
the same state. On the same host, claude --continue / --resume and
codex resume restore the session itself.
Arguments
Parse these from the user's invocation (any order):
| Arg | Required | Default | Meaning |
|---|---|---|---|
--out <path> |
no | .workspace/transitions/$(date -u +%Y-%m-%d)/$(date -u +%H%M%S).md |
Where to write |
--why <reason> |
no | "session boundary" | Short label appearing in TL;DR |
--title <text> |
no | inferred from recent commits and tasks | H1 title |
--dry-run |
no | false (write) | Print the file to stdout instead of writing |
Always write under .workspace/transitions/ — never under .claude/ or
.codex/. The shared path is load-bearing for cross-host continuation.
File structure (mandatory)
The file MUST have these sections, in this order. The structure is what
/continue reads — deviating breaks the contract.
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.
- 4d ago Changed · +4 lines aaf907f70c13
- 1mo ago Changed · -37 tokens per session c50343120440
- 1mo ago First seen · 294 lines · 91 tokens per session scan A 0ad50567485a
handoff is a skill published in the GitHub repository stefan-jansen/coding-agent-toolkit (33 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 2,747 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-30.
Other skills, from other repositories
knowledge-ingest
Ingest documents, articles, conversations, or supplied text into Knowledge with retained originals, sourced claims, entity updates, timelines, 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…
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…
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…
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…