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/chris-dare-dev/agent-kit/handoffnpx skills add chris-dare-dev/agent-kit --skill handoffgit clone --depth 1 https://github.com/chris-dare-dev/agent-kitWhat 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 | $0.00187 | $0.02791 |
| Opus 5 | $0.00093 | $0.01396 |
| Sonnet 5 | $0.00037 | $0.00558 |
| Haiku 4.5 | $0.00019 | $0.00279 |
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 yesterday.
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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff
Author continuation and/or review handoffs against the canonical contract in
.claude/references/handoff-contract.md, validate them with
.claude/scripts/handoff-validate.py, and wire review handoffs into the roadmap as optional
audit checkpoints. Works identically from Claude Code, Codex, and OpenCode — the contract and
validator are provider-neutral; the Obsidian surfacing step degrades gracefully on machines
without the vault tooling.
Continuations are live documents, not snapshots. When the workstream store is available
(contract §2a, workstream-state.md), the continuation handoff is
Workstreams/<slug>/continuation.md — one mutable file per workstream, gist-backed so every
machine sees the same state — and this skill UPDATES it in place rather than minting a dated
file. Review handoffs stay dated snapshots in the same workstream directory. The legacy
plans/HANDOFF-<date>-... form is the fallback for machines without the store.
When NOT to use
- To record a durable lesson or preference — that's
/memory-sync/ memory, not a handoff. - To advance or close a milestone —
/milestone-pipelineowns execution state; a handoff only describes it. - Mid-task context notes for yourself — handoffs are session-boundary artifacts.
Arguments
/handoff [continuation|review|both] [project-slug] [free-text notes]
- kind — omit to decide from the session: shipped milestone-scale work (commits landed across
≥1 milestone) →
both; mid-stream or light session →continuationonly. Say which you chose and why in the final report. - project-slug — omit to infer from the session's roadmap/milestone ids. This is the program
slug (e.g.
identity-seed,svcreg-supplychain-trust), used in the filename,project:frontmatter, and roadmap lookup. - notes — anything the user wants emphasized (e.g. "reviewer should focus on the live flip").
Steps
- Read the contract first:
.claude/references/handoff-contract.md— filename grammar, frontmatter schema, both body templates, the review-checkpoint format. Do not improvise frontmatter keys; legacy variants (type: session-handoff,handoff-kind:) break the vault Bases.
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.
- yesterday First seen · 201 lines · 187 tokens per session scan A db42e8baebb0
handoff is a skill published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 24d ago), licensed MIT. It adds 187 tokens to every session and 2,791 once invoked, about $0.0009 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
ask-user
You MUST use this before high-stakes architectural decisions, irreversible changes, or when requirements are ambiguous. Runs a decision handshake with the askuser tool: summarize context, present structured options, collect explicit user choice, then proceed.
kiwix
Search and read articles from a local Kiwix server — offline Wikipedia, documentation, Stack Exchange, and other ZIM content. Use when the user asks to look something up, find documentation, or read an article from local knowledge bases.
algolia-autocomplete
Building autocomplete and search-suggestion experiences with the Algolia Autocomplete UI library — distinct from InstantSearch. Covers query suggestions, multi-source autocomplete (suggestions + recent searches + records + redirects + content), the plugin architecture (@algolia/autocomplete-plugin-), keyboard nav…
algolia-contentful-integration
The Contentful ↔ Algolia integration we ship by default on Composable DXP engagements — choosing between the Marketplace app, the Ingestion API source connector, and a custom Vercel-Function indexer; mapping Topics & Assemblies to Algolia records; per-locale fan-out; preview vs. delivery indices; webhook signature…
algolia-index-design
Index and record design for Algolia — designing the JSON record shape that powers search, deciding searchable vs. faceted vs. displayed attributes, choosing per-type indices vs. one federated index, structuring distinct/grouping for variant collapse, and architecting replicas (standard vs. virtual) for sort orders.…
algolia-indexing-pipeline
Getting data into Algolia — full reindex vs. partial updates, atomic replacement via replaceAllObjects, batch sizing, idempotency, streaming pipelines (webhook-driven incremental sync), backfills, the Ingestion API for managed source connectors, and the Slalom default pattern of Vercel Functions + Contentful webhooks…