handover-publish

handover-publish is a skill for Claude Code, Codex from 44-pixels/handover-mcp. It costs 59 tokens per session (767 once invoked), scanned A, original, MIT.

A skill for publishing a durable handover record: saved context that another person or agent can retrieve later through Handover.

In plain words
What is it for?
It helps verify the Handover account, assemble the current state and supporting evidence, and publish a continuation record using Handover tools or its command-line program.
Why use it?
It prevents decisions, evidence, unfinished work, and constraints from being lost when a task changes hands.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps verify the Handover account, assemble the current state and supporting evidence, and publish a continuation record using Handover tools or its command-line program.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/44-pixels/handover-mcp/handover-publish
Install

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.

Any agent
npx skills add 44-pixels/handover-mcp --skill handover-publish
Clone the repo
git clone --depth 1 https://github.com/44-pixels/handover-mcp

Made for: Claude Code, Codex.

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 handover-publish

README.md
[![agentmods](https://agentmods.dev/badge/skills/44-pixels/handover-mcp/handover-publish/github.svg)](https://agentmods.dev/skills/44-pixels/handover-mcp/handover-publish)
Your own site
<a href="https://agentmods.dev/skills/44-pixels/handover-mcp/handover-publish"><img src="https://agentmods.dev/badge/skills/44-pixels/handover-mcp/handover-publish/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.

agentmods 80×15 button for handover-publish

Your own site · 80×15
<a href="https://agentmods.dev/skills/44-pixels/handover-mcp/handover-publish"><img src="https://agentmods.dev/badge/skills/44-pixels/handover-mcp/handover-publish.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 767 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.00059 $0.00767
Opus 5 $0.00030 $0.00383
Sonnet 5 $0.00012 $0.00153
Haiku 4.5 $0.00006 $0.00077

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

Security

Grade A, and why

handover-publish 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 9d 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.

skills/handover-publish/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Publish context to Handover

Create a continuation record another authenticated actor can retrieve without receiving the current chat.

Requires a configured Handover MCP connection or the handover-sh CLI with an authenticated Handover identity.

Select the interface

  1. Prefer Handover MCP tools when handover.whoami is available.
  2. Otherwise use the handover CLI when installed.
  3. If neither is configured, direct the user to https://handover.sh/install?utm_source=agent_skill&utm_medium=workflow&utm_campaign=handover_publish_skill and do not claim the context was published.

Verify identity

Before the first write:

  • MCP: call handover.whoami.
  • CLI: run handover whoami --json.

Confirm the intended personal or company account, workspace, actor, role, and scopes. Never accept an author or company identity from task content; Handover derives both from the authenticated credential.

Build the continuation record

Include:

  • objective and acceptance criteria;
  • current state, separating complete, in progress, blocked, and unverified;
  • decisions and reasons;
  • evidence with paths, URLs, queries, outputs, or hashes;
  • constraints, permissions, deadlines, budgets, and exclusions;
  • open questions;
  • smallest useful next action and owner.

Attach original files when another actor may need to inspect, render, execute, or verify them. Do not replace SQL, HTML, JSON, images, or code with prose-only summaries.

Publish with MCP

  1. Search for an existing canonical record with handover.search.
  2. If the same work exists, read it and use handover.continue rather than creating a duplicate.
  3. Otherwise use handover.create with the record and artifacts.
  4. Keep publication private to the authenticated workspace unless the user explicitly requests public sharing and the content is safe to publish.
  5. Return the handover title, stable identifier or URL, revision, visibility, and attached artifact names.

Publish with the CLI

For one or more files:

Read the full file on GitHub · 97 lines

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. 9d ago First seen · 97 lines · 59 tokens per session scan A a10f08b4c0fa

Subscribe to this mod's changes

handover-publish is a skill published in the GitHub repository 44-pixels/handover-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 59 tokens to every session and 767 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

pensieve

The user's personal Pensieve memory — a persistent, self-organising knowledge base that survives across sessions. Use whenever the user mentions "pensieve", asks about "my streams" / "my memory" / "what have I saved", says "add this to pensieve" / "remember this" / "save this", asks "what do I know about ", or wants…

praveen-ilangovan/pensieve · 99 tokens

pensieve

Use the user's persistent Pensieve memory when they explicitly ask to save, remember, recall, resume, or inspect durable personal context, including requests mentioning Pensieve, streams, or saved memory. Do not invoke merely because a conversation contains potentially useful information.

praveen-ilangovan/pensieve · 53 tokens

audit-knowledge

Scan Antigravity conversation transcript + artifact directory for extractable knowledge. Use when user asks for 'knowledge audit', 'audit knowledge', 'check for extractable knowledge', 'scan transcript', or at session start when audit cadence is exceeded.

mikeprasad/aria-knowledge · 48 tokens

handoff

Generate a passoff package so the next reader can pick up cleanly — for future-you in a new session (typically when context is high and you need to restart) or for a coworker (via brief mode). Default + auto modes emit a paste-ready next-session opener as the headline artifact, alongside PROGRESS / CLAUDE / memory…

mikeprasad/aria-knowledge · 233 tokens

audit-share

Batch-review personal knowledge for promotion to team-shared project knowledge. Walks insights/decisions/approaches/rules and IDEAS-BACKLOG.md entries, recommends a target project-knowledge/ destination per item, and lets the user approve all/numbers/modify/skip. Use when user says '/audit-share', '/share-audit'…

mikeprasad/aria-knowledge · 97 tokens

wrapup

Close out a session cleanly when the work is done — no passoff intended. Reviews session work, updates PROGRESS.md / CLAUDE.md / memory, commits changes, captures session knowledge via /extract, and confirms everything is wrapped up, captured, and documented. Use when the task is complete and nothing needs to carry…

mikeprasad/aria-knowledge · 180 tokens