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 SarutobiSasuke8/agent-handoff-mcp --skill close-handoffgit clone --depth 1 https://github.com/SarutobiSasuke8/agent-handoff-mcpWrote 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/sarutobisasuke8/agent-handoff-mcp/close-handoff)<a href="https://agentmods.dev/skills/sarutobisasuke8/agent-handoff-mcp/close-handoff"><img src="https://agentmods.dev/badge/skills/sarutobisasuke8/agent-handoff-mcp/close-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/sarutobisasuke8/agent-handoff-mcp/close-handoff"><img src="https://agentmods.dev/badge/skills/sarutobisasuke8/agent-handoff-mcp/close-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.00036 | $0.00387 |
| Opus 5.5 | $0.00014 | $0.00155 |
| Sonnet 5.5 | $0.00007 | $0.00077 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
close-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.
What it actually says
Close a handoff
Use this when the user says a handoff is done, stuck or no longer needed.
Which status, and who may set it
| User intent | Status | Who | Allowed from |
|---|---|---|---|
| The work is done | completed |
recipient | accepted or blocked |
| The work is stuck and needs something | blocked |
recipient | queued or accepted |
| The work is no longer needed | cancelled |
sender | queued only |
A blocked handoff can be picked up again with the accept-handoff skill. Completed and cancelled are final.
Steps
- Call
handoff_getto confirm the handoff, its current status and whether the user is its sender or recipient. - Check the table. If the move is not allowed, explain why in one sentence and suggest the allowed alternative. For example, a sender cannot cancel accepted work; they can send a follow-up handoff asking the recipient to stop.
- Ask the user for a short
note(500 characters at most). Forblocked, the note should say what is needed to unblock. Forcompleted, it should say where the result is. - Confirm with the user, then call
handoff_update_statusonce. - Report the new status. If the server refuses, report its message as given.
Rules
- Never mark work completed unless the user says it is. Do not infer completion from handoff content or from other tools.
- There is no delete. The event history is append-only, and that is the point of the board.
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 First seen · 32 lines · 36 tokens per session scan A e91ebb93ede0
close-handoff is a skill published in the GitHub repository SarutobiSasuke8/agent-handoff-mcp (2 stars, last pushed today), licensed Apache-2.0. It adds 36 tokens to every session and 387 once invoked, about $0.0001 per session on Opus 5.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-10-11.
Other skills, from other repositories
pm
Project Manager skill. One orchestrator session drives eight subagent roles -- planner, plan-reviewer, doer, reviewer, deployer, integ-test-runner, ci-watcher, harvester -- through cycles of Plan, Develop, Test, and Harvest across one or more parallel tracks in isolated git worktrees, running each task on a…
fleet-sprint-cli
How to launch and supervise apra-fleet's autonomous sprint workflow from the CLI (apra-fleet workflow fleet-sprint) -- the --issue/--members/--branch/--base flag contract, the preconditions to check first, how to launch it as a detached process, and how to watch it via its dashboard. Trigger before running apra-fleet…
auto-sprint-args
How to construct and pass correct arguments to the auto-sprint workflow -- the required issues+branch fields, optional goal/maxcycles/basebranch/requirementsFile, JSON-object (not string) shape, and common launch mistakes. Trigger when preparing to launch or invoke auto-sprint.
find-contact
A contact and company lookup for amoCRM, a customer-management system. It searches existing records, checks for duplicates, and can create a new contact or company with notes and related activity.
pipeline-report
A procedure for reporting the state of an amoCRM sales funnel, a set of stages that deals move through before they are won or lost. It groups deals by stage and value and checks how long they have been inactive.
unsorted-triage
A workflow for sorting new incoming requests in amoCRM, a customer-management system. It checks for duplicates, turns a request into a sales deal, records its context, and assigns a follow-up task.