handoffkit-scaffold

handoffkit-scaffold is a skill for Codex from dyngai/handoffkit. It costs 108 tokens per session (1,255 once invoked), scanned C, original, MIT.

A skill that scaffolds HandoffKit-style coordination building blocks into Go projects. These include message mailboxes, routing, barriers, tracing, budgets, supervision, and handling failed messages.

In plain words
What is it for?
Use it to add these runtime primitives to an existing Go module, including projects that need explicit handoffs, bounded coordination, or execution tracing.
Why use it?
It gives a Go project a defined starting structure for agents or components that need to pass work, coordinate, and remain inspectable.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit Use it to add these runtime primitives to an existing Go module, including projects that need explicit handoffs, bounded coordination, or execution tracing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dyngai/handoffkit/handoffkit-scaffold
Install

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.

Any agent
npx skills add dyngai/handoffkit --skill handoffkit-scaffold
Clone the repo
git clone --depth 1 https://github.com/dyngai/handoffkit

Made for: Codex.

Wrote 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.

agentmods badge for handoffkit-scaffold

README.md
[![agentmods](https://agentmods.dev/badge/skills/dyngai/handoffkit/handoffkit-scaffold/github.svg)](https://agentmods.dev/skills/dyngai/handoffkit/handoffkit-scaffold)
Your own site
<a href="https://agentmods.dev/skills/dyngai/handoffkit/handoffkit-scaffold"><img src="https://agentmods.dev/badge/skills/dyngai/handoffkit/handoffkit-scaffold/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.

agentmods 80×15 button for handoffkit-scaffold

Your own site · 80×15
<a href="https://agentmods.dev/skills/dyngai/handoffkit/handoffkit-scaffold"><img src="https://agentmods.dev/badge/skills/dyngai/handoffkit/handoffkit-scaffold.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 108 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,255 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00108 $0.01255
Opus 5 $0.00054 $0.00628
Sonnet 5 $0.00022 $0.00251
Haiku 4.5 $0.00011 $0.00126

Measured 9d ago against content hash b55c8b1b47a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade C, and why

handoffkit-scaffold scanned grade C with 1 finding 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 9d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

is there. Do not overwrite, delete, merge into, or `rm -rf` those
plugins/handoffkit/skills/handoffkit-scaffold/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scaffold PlatformPilot-style HandoffKit primitives into Go

Use this to add the DynG AI (https://dyng.ai) HandoffKit message-passing runtime to a Go project: the practical, PlatformPilot (https://platformpilot.ai) inspired foundation for explicit agent handoffs, inspectable routing, bounded fan-in, and traceable coordination. The reference sources are vendored under this skill's references/_src/ directory, a snapshot of the canonical runtime, so this works offline. (The _src name keeps the go tool from compiling these reference files as part of the HandoffKit module.)

This is the Go reference implementation, one instantiation of the pattern. The pattern itself is language-agnostic: for a Python, TypeScript, Rust, or Erlang project there is nothing to copy, use the handoffkit skill and build the equivalent from its primitive→language mapping table.

Steps

  1. Determine the target module path. Read the project's go.mod. If there is none, ask the user for a module path and run go mod init <path>. The scaffolded runtime requires Go 1.21+. The full HandoffKit repo requires Go 1.22+ because of its OpenAI SDK dependency.

  2. Choose package destinations and protect existing code. Before copying, inspect the target paths you plan to use.

    • Default destinations are sketch/ and runtime/.
    • If either path already exists and contains files, stop and summarize what is there. Do not overwrite, delete, merge into, or rm -rf those directories implicitly.
    • Ask the user whether to overwrite/merge into those paths, or choose an alternate namespace such as internal/handoffkit/sketch and internal/handoffkit/runtime.
    • If you choose alternate paths, keep the same relative shape (sketch beside runtime) and rewrite imports to that alternate sketch package.
  3. Copy the reference sources from this skill into the chosen destinations, preserving structure, tests, and license attribution:

    • references/_src/sketch/*.go<sketch destination>/
    • references/_src/runtime/*.go<runtime destination>/
    • Include _test.go files. They are part of the scaffolded confidence boundary and let the target project verify the copied runtime directly.
    • The copied files are MIT-licensed HandoffKit source. Preserve attribution by either copying the bundled HandoffKit license from this repo's root LICENSE file alongside the scaffolded HandoffKit code, or creating/updating the target project's third-party notices file with the HandoffKit name, source URL https://github.com/dyngai/handoffkit, MIT license, and full license text from that bundled root LICENSE file.

Read the full file on GitHub · 84 lines

Changes

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.

  1. 9d ago First seen · 84 lines · 108 tokens per session scan C b55c8b1b47a5

Subscribe to this mod's changes

handoffkit-scaffold is a skill published in the GitHub repository dyngai/handoffkit (28 stars, last pushed 2mo ago), licensed MIT. It adds 108 tokens to every session and 1,255 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

neo4j-driver-go-skill

Covers the Neo4j Go Driver v6 — driver lifecycle, ExecuteQuery, managed and explicit transactions, session config, error handling, data type mapping, and connection tuning. Use when writing Go code that connects to Neo4j, setting up NewDriver or ExecuteQuery, debugging sessions/transactions/result handling, or working…

neo4j-contrib/neo4j-skills · 143 tokens

go-style

Modern Go code style for stdlib-first programs — error wrapping with %w, sentinel errors, structured logging with log/slog, context threading, consumer-defined interfaces, nil-safe constructors, net/http servers with method-pattern routing, flag/env configuration for services, and cobra commands with viper…

bitwise-media-group/skills · 0 tokens

golang-documentation

Comprehensive documentation guide for Golang projects, covering godoc comments, README, CONTRIBUTING, CHANGELOG, Go Playground, Example tests, API docs, and llms.txt. Use when writing or reviewing doc comments, documentation, adding code examples, setting up doc sites, or discussing documentation best practices.…

aiskillstore/marketplace · 77 tokens

golang-modernize

Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Use when reviewing Go code with old-style patterns, when encountering a deprecation warning, or when the user asks for modernization, a Go version upgrade (e.g. to Go 1.27), or a CI/tooling refresh. Not for…

aiskillstore/marketplace · 105 tokens

golang-samber-slog

Structured logging extensions for Golang using samber/slog- packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog…

aiskillstore/marketplace · 123 tokens

golang-cli

Golang CLI application development. Use when building, modifying, or reviewing a Go CLI tool — especially for command structure, flag handling, configuration layering, version embedding, exit codes, I/O patterns, signal handling, shell completion, argument validation, and CLI unit testing. Also triggers when code uses…

aiskillstore/marketplace · 126 tokens