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 alphaelements/handoff-mcp --skill handoff-importgit clone --depth 1 https://github.com/alphaelements/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-import)<a href="https://agentmods.dev/skills/alphaelements/handoff-mcp/handoff-import"><img src="https://agentmods.dev/badge/skills/alphaelements/handoff-mcp/handoff-import/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/alphaelements/handoff-mcp/handoff-import"><img src="https://agentmods.dev/badge/skills/alphaelements/handoff-mcp/handoff-import.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.00066 | $0.02237 |
| Opus 5.5 | $0.00026 | $0.00895 |
| Sonnet 5.5 | $0.00013 | $0.00447 |
| Haiku 4.5 | $0.00007 | $0.00224 |
Grade A, and why
handoff-import 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 3d 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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handoff Import
Import an existing handoff document (Markdown, JSON, or free-text) into
structured .handoff/ management via a single handoff_import_context call.
Usage
/handoff-import tmp/260601-sprint-handoff.md
/handoff-import path/to/any-document.md
If called without arguments, ask the user for a file path.
Procedure
-
Init check: Verify
.handoff/exists. If not, runhandoff_initfirst. -
Read the source: Read the specified file with the Read tool.
-
Analyze and structure: Decompose the content into the categories below.
-
Import: Call
handoff_import_contextonce with all extracted data. -
Report: Show how many tasks were created, whether a session was saved, and whether raw_notes captured anything.
-
Verify: Call
handoff_list_tasksto display the import result and ask the user to confirm correctness.
Field Mapping Guide
tasks — Extracting Structured Tasks
Every actionable item in the source document becomes a task. Always populate these fields:
| Field | How to extract |
|---|---|
title |
Short imperative phrase (e.g. "Add retry logic to USB reconnect") |
status |
Map from source: "done"/"completed" -> done, "WIP"/"in progress" -> in_progress, "blocked" -> blocked, else todo |
priority |
See priority rules below. Must be low, medium, or high |
notes |
Context that doesn't fit elsewhere: root cause, constraints, approach taken |
labels |
Category tags from the source (e.g. ["auth", "security"], ["pio", "dma"]) |
links |
Related file paths, issue URLs, MR URLs, wiki pages |
done_criteria |
Verifiable checklist items extracted from prose (see below) |
children |
Sub-tasks nested under a parent |
schedule.estimate_hours |
If effort estimates are mentioned (e.g. "~2h", "half a day") |
schedule.due_date |
If deadlines are mentioned (ISO format) |
schedule.milestone |
If milestone names are mentioned |
dependencies |
Task IDs this task depends on (e.g. "after t1", "once X is done") |
order |
Display ordering hints (e.g. P0→P1→P2 maps to 0, 1, 2) |
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.
- 3d ago Changed 29c58778bec7
- 1mo ago First seen · 239 lines · 66 tokens per session scan A 47ec60937acb
handoff-import is a skill published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 66 tokens to every session and 2,237 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…