Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add alphaelements/handoff-mcp/plugin install 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/alphaelements/handoff-mcp/handoff-refer)<a href="https://agentmods.dev/skills/alphaelements/handoff-mcp/handoff-refer"><img src="https://agentmods.dev/badge/skills/alphaelements/handoff-mcp/handoff-refer.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.00054 | $0.00638 |
| Opus 5 | $0.00027 | $0.00319 |
| Sonnet 5 | $0.00011 | $0.00128 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
handoff-refer 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 7d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Refer Skill
Send a structured referral (improvement request, bug report, work request) from the current project to another project that uses handoff-mcp.
When to Use
- You discover a bug in a dependency project during work
- You identify an improvement needed in another project
- You want to request work from another team/project
- Cross-project coordination is needed
Procedure
- Identify the target project (by name or path).
- Determine the referral type:
improvement,bug,request, orinfo. - Call
handoff_referwith all required fields:summary: one-line descriptionreferral_type: categorypriority:low,medium, orhightarget_project(name) ortarget_project_dir(path)details: what changed, its impact, and what the target needs to dotasks: concrete work items withdone_criteriacontext: source references (branch, commit, spec docs, MR links)
- If warnings are returned, fix them before proceeding. The server
validates completeness — omitting
details,tasks,context, orprioritytriggers warnings. Tasks withoutdone_criteriaalso warn. - Report confirmation to the user.
Target Resolution
- By name:
target_project: "pochi-dio"— resolved viascan_dirsin config - By path:
target_project_dir: "/home/user/pro/pochi-dio"— direct path
Use name when the project is in a scan_dirs directory. Use path when targeting a project outside scan_dirs.
Managing Received Referrals
When handoff_load_context shows incoming referrals:
- Review each referral's summary and priority.
- Acknowledge with
handoff_update_referral(status:acknowledged). - Create tasks based on the referral if appropriate.
- Resolve with
handoff_update_referral(status:resolved) when done.
Example
{
"target_project": "handoff-mcp",
"summary": "Import skill needs better task structuring guidance",
"referral_type": "improvement",
"priority": "medium",
"details": "When importing 20 tasks from pochi-dio, done_criteria and links were mostly empty.",
"tasks": [
{
"title": "Add before/after examples to import skill",
"priority": "medium",
"done_criteria": [
{"item": "Skill includes concrete field mapping examples"}
]
}
]
}
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 72 lines · 54 tokens per session scan A 29a22cc9c467
handoff-refer is a skill published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 54 tokens to every session and 638 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.