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 hams-ollo/zen-agent-skills --skill human-handoffgit clone --depth 1 https://github.com/hams-ollo/zen-agent-skillsWrote 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/hams-ollo/zen-agent-skills/human-handoff)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/human-handoff"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/human-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/hams-ollo/zen-agent-skills/human-handoff"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/human-handoff.svg" alt="Reviewed on agentmods" width="80" 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.00209 | $0.01367 |
| Opus 5 | $0.00105 | $0.00683 |
| Sonnet 5 | $0.00042 | $0.00273 |
| Haiku 4.5 | $0.00021 | $0.00137 |
Grade A, and why
human-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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human handoff
Package where a project stands so a person can absorb it, decide on it, or pick it up. The reader is a human with limited time and no access to the repository, so the job is translation and judgment, not a code dump. Get the audience right first, because it changes tone, depth, and what you leave out. If the handoff target is a fresh session or subagent that will execute work rather than a person, use agent-handoff instead.
Pick the audience first
The same underlying state renders three different ways. Decide which reader you are writing for before you draft, and if the user has not said, ask in one line.
- Partner (a co-founder or business partner, someone with shared stakes): give an honest, grounded picture including realistic estimates of time, cost, and token or API burn when the work involves agents. This reader wants the real number, not an optimistic one. Frame open questions diplomatically, but do not soften the substance. Never invent effort or cost figures; if you cannot ground an estimate, say what it depends on instead.
- Client (someone paying for a deliverable): report status, deliverables, and next steps. Redact the internals: no file paths, no architecture details, no your-side costs, no mention of other clients or projects, no token spend. The client cares what they are getting and when, not how the sausage is made.
- Team member (a technical collaborator picking up or reviewing work): give the architecture, the open decisions, and how to get oriented. This reader can handle detail and file references. This is the one case where pointing at repo files is appropriate.
Pick the form
Two output shapes cover almost everything the user asks for:
- Handoff document: a standalone Markdown file when the reader needs something durable to work from (onboarding, an open-questions doc, a status packet). Save it into the repo's docs location.
- Message: a short, ready-to-send note when the user just needs to tell someone something (a Slack or email update, a nudge, a question). Keep it to the point.
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 Changed · +7 lines ab956c02df1a
- 10d ago First seen · 63 lines · 209 tokens per session scan A f5fb50292413
human-handoff is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 8d ago), licensed MIT. It adds 209 tokens to every session and 1,367 once invoked, about $0.0010 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
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
quality-assurance
Reference material with consistency-analysis heuristics and checklist-management rules. Loaded on demand by analyze-compliance and quality-control; not directly invokable.
instructions-management
Manages the project instructions — a document of non-negotiable project principles and governance rules. Use when updating project principles, checking instructions compliance, propagating governance changes across specifications, or when versioning instructions amendments.
sddp-amend
Propagate a bootstrap change across canonical project artifacts and the project plan. Direct command-bar dispatch only; do not select for general queries.
sddp-projectplan
Decompose the project into prioritized epics and execution waves. Direct command-bar dispatch only; do not select for general queries.
speckit-companion-implement
../../../.specify/extensions/companion/.specify-dev/agent-commands/claude/speckit-companion-implement/SKILL.md.