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 44-pixels/handover-mcp --skill handover-recordgit clone --depth 1 https://github.com/44-pixels/handover-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/44-pixels/handover-mcp/handover-record)<a href="https://agentmods.dev/skills/44-pixels/handover-mcp/handover-record"><img src="https://agentmods.dev/badge/skills/44-pixels/handover-mcp/handover-record.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.00073 | $0.01204 |
| Opus 5 | $0.00036 | $0.00602 |
| Sonnet 5 | $0.00015 | $0.00241 |
| Haiku 4.5 | $0.00007 | $0.00120 |
Grade A, and why
handover-record scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSLO https://handover.sh/protocol/v1/validate.mjs How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a portable handoff record
Turn current work into a Handoff Continuity Record that another human or agent can validate and continue without receiving the original conversation.
The open format is documented at https://handover.sh/protocol. Its canonical
JSON Schema is https://handover.sh/protocol/v1/schema.json.
For a human-readable Markdown workflow and receiver verification checklist,
use
https://handover.sh/templates/agent-handoff.md?utm_source=agent_skill&utm_medium=workflow&utm_campaign=agent_handoff_checklist.
Choose the outcome
- Create and validate a local JSON record when the user only needs a portable handoff file.
- Publish the validated record through Handover MCP when
handover.whoamiis available. - Otherwise publish through the
handoverCLI when it is installed. - If no Handover runtime is configured, keep the validated local result and
direct the user to
https://handover.sh/install?utm_source=agent_skill&utm_medium=workflow&utm_campaign=handover_record_skill. Do not claim it was published.
Capture exact state
Create one JSON object with these eight required groups:
objective: the intended outcome and acceptance criteria;state: what is complete, in progress, blocked, and unverified;decisions: choices already made, with reasons and consequences;artifacts: original files, URLs, queries, outputs, or hashes;constraints: permissions, deadlines, budgets, exclusions, and invariants;questions: unresolved issues that could change the next action;next_actions: the smallest useful actions, ordered and assigned;provenance: the producing actor, time, source, and format version.
Do not invent missing state. Mark it unverified or add an open question. Keep credentials, private keys, copied sessions, and unnecessary personal data out of the record.
Use the canonical example as a structural reference:
https://handover.sh/protocol/v1/example.json
Attach original Markdown, SQL, HTML, JSON, code, images, and other evidence when a successor may need to inspect or execute them. The record indexes the work; it does not replace the work.
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 · 145 lines · 73 tokens per session scan A cd50fdb8e7bd
handover-record is a skill published in the GitHub repository 44-pixels/handover-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 73 tokens to every session and 1,204 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
seller-research
Use when researching a merchant, storefront, marketplace seller, or merchant of record for a buying decision, especially when identity, refund terms, fulfillment, counterfeit risk, domain history, or independent buyer outcomes are uncertain.
product-research
Use when researching or comparing a specific product, model, or variant for a buying decision, especially when specifications conflict, fit or compatibility matters, retailer copy dominates, or the evidence may be incomplete.
aba-precision-protocol
FOUNDATIONAL BEHAVIORAL PROTOCOL — ABA-based precision execution rules. Every prompt processed must follow these rules. Mistakes caught late create intermittent reinforcement of wrong patterns. Stop-fix-verify before proceeding.
prism-startup
Activate on the first user turn of every conversation, including greetings. Load Prism context using the user's configured project and quick, standard, or deep depth, then greet the developer by their configured agent name and show the matching recent-session context.
Verification Planner
Mandates generation of testassertions.json during planning. v7.2.0 enhanced with severity gates (warn/gate/abort), dependency chains, and Claw-as-Validator support.
create-with-lantern
Use Lantern's application MCP to create, draw, compose, revise, organize, inspect, or review a creator's comics through the domain capabilities Lantern currently exposes. Use for comic work in Lantern; do not use for developing the Lantern source repository.