handoff-refer

handoff-refer is a skill for Claude Code, Codex from alphaelements/handoff-mcp. It costs 54 tokens per session (638 once invoked), scanned A, original, MIT.

A skill for sending structured work referrals between projects through a project's handoff folder.

In plain words
What is it for?
Use it to report bugs, request improvements or work, or share information with another project.
Why use it?
It records the issue or request with its priority, context, tasks, and completion conditions so another project can act on it.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /home/user/pro/pochi-dio.

Part of the handoff-mcp plugin — 6 skills shipped together

Good fit Use it to report bugs, request improvements or work, or share information with another project.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add alphaelements/handoff-mcp
Claude Code
/plugin install handoff-mcp

Made for: Claude Code, Codex.

Or install handoff-mcp, the plugin that ships this one along with the rest of its 6 skills.

Wrote 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.

agentmods badge for handoff-refer

README.md
[![agentmods](https://agentmods.dev/badge/skills/alphaelements/handoff-mcp/handoff-refer.svg)](https://agentmods.dev/skills/alphaelements/handoff-mcp/handoff-refer)
Your own site
<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>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 638 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash 29a22cc9c467, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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.

plugin/skills/handoff-refer/SKILL.md · 72 lines

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

  1. Identify the target project (by name or path).
  2. Determine the referral type: improvement, bug, request, or info.
  3. Call handoff_refer with all required fields:
    • summary: one-line description
    • referral_type: category
    • priority: low, medium, or high
    • target_project (name) or target_project_dir (path)
    • details: what changed, its impact, and what the target needs to do
    • tasks: concrete work items with done_criteria
    • context: source references (branch, commit, spec docs, MR links)
  4. If warnings are returned, fix them before proceeding. The server validates completeness — omitting details, tasks, context, or priority triggers warnings. Tasks without done_criteria also warn.
  5. Report confirmation to the user.

Target Resolution

  • By name: target_project: "pochi-dio" — resolved via scan_dirs in 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:

  1. Review each referral's summary and priority.
  2. Acknowledge with handoff_update_referral (status: acknowledged).
  3. Create tasks based on the referral if appropriate.
  4. 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"}
      ]
    }
  ]
}

Read the full file on GitHub · 72 lines

Files

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.

Changes

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.

  1. 7d ago First seen · 72 lines · 54 tokens per session scan A 29a22cc9c467

Subscribe to this mod's changes

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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

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.

wshobson/agents · 54 tokens