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 Wh0FF24/whoff-agents --skill agent-handoffgit clone --depth 1 https://github.com/Wh0FF24/whoff-agentsWrote 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/wh0ff24/whoff-agents/agent-handoff)<a href="https://agentmods.dev/skills/wh0ff24/whoff-agents/agent-handoff"><img src="https://agentmods.dev/badge/skills/wh0ff24/whoff-agents/agent-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/wh0ff24/whoff-agents/agent-handoff"><img src="https://agentmods.dev/badge/skills/wh0ff24/whoff-agents/agent-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.00019 | $0.01062 |
| Opus 5 | $0.00010 | $0.00531 |
| Sonnet 5 | $0.00004 | $0.00212 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
agent-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 8d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Handoff Skill
You are preparing a handoff packet — the minimum context a subagent needs to execute correctly without asking clarifying questions, re-exploring dead ends, or hallucinating constraints.
Subagents fail for one reason: they receive a goal but not its shape. They don't know what you already tried, what's off-limits, what "done" looks like, or which files actually matter. This skill makes that implicit context explicit.
What You Will Do
-
Extract from the current session:
- The exact task to delegate (one sentence, actionable)
- Decisions already made that the subagent must not re-litigate
- Approaches tried and ruled out (with reasons)
- Files/paths the subagent needs to touch (concrete, not vague)
- The success criterion — how the subagent knows it's done
- Hard constraints — what it must not do
-
Write the handoff packet to
.claude/handoff-<timestamp>.md:
# Agent Handoff — <ISO timestamp>
## Objective
[One sentence. Starts with a verb. Specific enough that no clarifying question is needed.]
## Context the subagent needs
- [Key fact 1 — architectural decision, API behavior, business rule]
- [Key fact 2]
- [Add only what would not be obvious from reading the files]
## Already tried — do not re-attempt
- [Approach]: [Why it failed or was ruled out]
- [Approach]: [Why it failed or was ruled out]
## Files to touch
- `path/to/file.ts` — [what to do here, optionally line number]
- `path/to/other.ts` — [what to do here]
## Hard constraints
- [MUST NOT]: [What the subagent must not change, call, or assume]
- [MUST NOT]: [...]
## Success criterion
- [ ] [Concrete, verifiable output — test passes, file exists, API returns X]
- [ ] [Second criterion if needed]
## If blocked
[What the subagent should do if it hits an unexpected blocker — escalate, write a findings file, skip and note, etc.]
-
Echo the packet so you can verify it before dispatching.
-
Copy the packet content into your Agent tool prompt or tmux dispatch command so the subagent has it inline.
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.
- 8d ago First seen · 87 lines · 19 tokens per session scan A bfebb8c1a58d
agent-handoff is a skill published in the GitHub repository Wh0FF24/whoff-agents (2 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 1,062 once invoked, about $0.0001 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
shogun-bloom-config
An interactive wizard that creates model-routing settings from your AI subscription choices. Model routing decides which available model handles each kind of task.
shogun-screenshot
A screenshot tool for getting images from a computer or web page and then cropping, resizing, or masking sensitive information. Playwright is a browser-automation tool used here to capture web pages.
shogun-model-list
A reference table of AI command-line tools, their available models, subscription requirements, and maximum Bloom capability levels. Bloom's Taxonomy is a scale describing thinking tasks, from remembering information to creating new designs.
shogun-model-switch
A live-switching tool for changing which command-line AI agent, model, and reasoning mode is running. It updates settings, restarts the agent, and refreshes the displayed session information.
shogun-readme-sync
A skill that compares an English README with its Japanese counterpart and brings them back into alignment. A README is the project document that explains what the software is and how to use it.
shogun-agent-status
A skill that shows whether the agents in a multi-agent Japanese feudal-themed team are working, waiting, missing, or assigned tasks. It combines terminal session status, task files, and unread messages.