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/wardmos/waybill/handoffnpx skills add wardmos/waybill --skill handoffgit clone --depth 1 https://github.com/wardmos/waybillWrote 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/wardmos/waybill/handoff)<a href="https://agentmods.dev/skills/wardmos/waybill/handoff"><img src="https://agentmods.dev/badge/skills/wardmos/waybill/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.00044 | $0.00168 |
| Opus 5 | $0.00022 | $0.00084 |
| Sonnet 5 | $0.00009 | $0.00034 |
| Haiku 4.5 | $0.00004 | $0.00017 |
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 5d 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.
What it actually says
Waybill Handoff for Claude Code
This is a thin Claude Code wrapper around the shared Waybill handoff workflow.
For exports, use claude-code as source_agent; never claim another product
created the bundle.
Arguments are available as $ARGUMENTS.
Read the shared dispatch completely and follow it,
using $ARGUMENTS as the request arguments.
/handoff is the primary command. /waybill is provided by the sibling alias
skill.
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.
- 5d ago First seen · 19 lines · 44 tokens per session scan A 177929f360b4
handoff is a skill published in the GitHub repository wardmos/waybill (41 stars, last pushed 5d ago), licensed Apache-2.0. It adds 44 tokens to every session and 168 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
mcp-media-inbox-triage
Find media, partnership, and high-intent requests buried in a shared Gmail inbox, summarize the useful ones, and route them to the right owner through Zapier MCP.
install-zapier
Install and connect Zapier, routing to the right surface (MCP, SDK, or CLI) for what the person needs. Use when someone says "install Zapier", "add Zapier", "connect Zapier", or "set up Zapier", or when they want an AI client (Claude, ChatGPT, Cursor) to use their apps, want to call Zapier from code, or want Zapier in…
shell-output-compaction
Reduce shell and tool-output token waste by preferring targeted commands, diff-only views, error-first logs, narrow slices, counts, and concise summaries instead of large raw stdout dumps. Use on coding, debugging, audits, CI triage, or repo exploration when command output is likely to dominate token usage.
rtk-assisted-shell
Reduce shell output token waste on git, file reads, searches, test runs, linters, logs, and other noisy developer commands with RTK-style filtering. Use when shell-heavy work is flooding the session with logs, diffs, or command output that should be compacted before it reaches the model.
token-efficient-execution
Reduce token waste in long coding-agent sessions by avoiding repeated reads, noisy output, oversized context, broad rewrites, and unnecessary narration. Use on long tasks, heavy repos, multi-file audits, shell-heavy debugging loops, or whenever token budget is a practical delivery constraint.
token-frugal-mode
Reduce output-token usage without losing technical accuracy. Use when the user asks to save tokens, be terse, stay brief, use caveman mode, use compressed answers, minimize chatter, or when the session is context-tight and the task does not need long prose.