plain-handoff

plain-handoff is a skill for Claude Code, Codex from benjaminard/fable-skills. It costs 63 tokens per session (609 once invoked), scanned A, original, MIT.

A closing-message guide for coding-agent sessions. It explains how to summarize completed work in plain language for someone who did not see the process.

In plain words
What is it for?
Use it when writing summaries after investigations, builds, long-running tasks, or other multi-step sessions.
Why use it?
It prevents final handoffs from relying on unexplained shorthand, missing important outcomes, or hiding what the user still needs to decide.

Skill for Claude CodeCodex

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

Good fit Use it when writing summaries after investigations, builds, long-running tasks, or other multi-step sessions.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/benjaminard/fable-skills/plain-handoff
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 benjaminard/fable-skills --skill plain-handoff
Clone the repo
git clone --depth 1 https://github.com/benjaminard/fable-skills

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 plain-handoff

README.md
[![agentmods](https://agentmods.dev/badge/skills/benjaminard/fable-skills/plain-handoff/github.svg)](https://agentmods.dev/skills/benjaminard/fable-skills/plain-handoff)
Your own site
<a href="https://agentmods.dev/skills/benjaminard/fable-skills/plain-handoff"><img src="https://agentmods.dev/badge/skills/benjaminard/fable-skills/plain-handoff/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 plain-handoff

Your own site · 80×15
<a href="https://agentmods.dev/skills/benjaminard/fable-skills/plain-handoff"><img src="https://agentmods.dev/badge/skills/benjaminard/fable-skills/plain-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 609 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.00063 $0.00609
Opus 5.5 $0.00025 $0.00244
Sonnet 5.5 $0.00013 $0.00122
Haiku 4.5 $0.00006 $0.00061

Measured 1mo ago against content hash 717ebffe1f7f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

plain-handoff 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 1mo 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/plain-handoff/SKILL.md · 42 lines

How it starts

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

Plain Handoff

Your final message is the user's first look at everything you did. Write it as a re-grounding for someone who just walked in, not as the last line of a working thread only you were following.

The re-grounding rule

While working, you built up context the user never saw: file names you discovered, labels you coined, intermediate findings, dead ends. None of that vocabulary is theirs. In the final message:

  1. Open with the outcome. One sentence on what happened or what you found, before any detail.
  2. Then the one or two things you need from them, each explained as if new.
  3. Retire your working shorthand. Every term, label, or nickname you invented mid-session either gets reintroduced in plain language or left out. "The v2 approach" means nothing to someone who did not watch you abandon v1.

Working notes are not the deliverable

Terse shorthand between tool calls is fine; that is you thinking out loud. The final summary is a different document with a different reader:

  • Write complete sentences. No arrow chains, no hyphen-stacked compounds, no fragment stacks.
  • Spell out terms and acronyms on first use.
  • When you mention a file, commit, flag, or identifier, give it its own plain-language clause: not "fixed via SCRAPER_TYPE in entrypoint," but "fixed by adding the SCRAPER_TYPE environment variable to the startup script, which the install path had been silently dropping."
  • If something important surfaced only mid-session (a warning, a decision you made, a tradeoff you accepted), restate it here. Anything not in the final message effectively did not happen.

Completeness check

Before sending, verify the summary answers, in order:

  1. What was the goal? (One clause; the user may be returning after hours.)
  2. What is the outcome? (Done, partially done, blocked, and on what evidence.)
  3. What changed? (Files, systems, state, in plain language.)
  4. What do you need from the user, if anything?
  5. What did you deliberately not do? (Out-of-scope findings, deferred work, known limitations.)

Read the full file on GitHub · 42 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. 1mo ago First seen · 42 lines · 0 tokens per session scan A 717ebffe1f7f

Subscribe to this mod's changes

plain-handoff is a skill published in the GitHub repository benjaminard/fable-skills (34 stars, last pushed 3mo ago), licensed MIT. It adds 63 tokens to every session and 609 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-30.

Related

Other skills, from other repositories

alterlab-qiime2-amplicon

Runs 16S/ITS amplicon (microbiome) analysis with the QIIME 2 distribution (2026.7; the "amplicon" distribution was renamed "qiime2" in 2026.4) in the correct order: manifest import, cutadapt trim-paired primer removal BEFORE dada2 denoise-paired (trunc-len chosen from the demux quality .qzv), feature-classifier…

AlterLab-IEU/AlterLab-Academic-Skills · 270 tokens

alterlab-paper-writer

Drafts and revises academic papers through a 12-agent pipeline with hardened LaTeX output (apa7 class, PDF compiled from LaTeX), supporting IMRaD, literature review, theoretical, case study, policy brief, and conference paper structures, APA 7.0 (default), Chicago, MLA, IEEE, and Vancouver citation formats, bilingual…

AlterLab-IEU/AlterLab-Academic-Skills · 271 tokens

alterlab-imaging-data-commons

Query and download public cancer imaging data from the NCI Imaging Data Commons (IDC) using the idc-index Python package, filtering by metadata, visualizing in-browser, and checking licenses, with no authentication required. Use when obtaining large-scale radiology (CT, MR, PET) or digital pathology DICOM datasets for…

AlterLab-IEU/AlterLab-Academic-Skills · 90 tokens

alterlab-phylogenetics

Build phylogenetic trees end-to-end from raw sequences — MAFFT multiple sequence alignment, optional TrimAl trimming, IQ-TREE 3 maximum-likelihood inference with model selection and bootstraps, FastTree for large datasets, then visualize with ETE3 or FigTree. Use when reconstructing trees from sequences (FASTA) for…

AlterLab-IEU/AlterLab-Academic-Skills · 152 tokens

alterlab-molecular-dynamics

Runs and analyzes molecular dynamics simulations with OpenMM and MDAnalysis — setting up protein and small-molecule systems, assigning force fields, running energy minimization and production MD, and analyzing trajectories (RMSD, RMSF, contact maps, free energy surfaces). Use when simulating protein or ligand…

AlterLab-IEU/AlterLab-Academic-Skills · 98 tokens

alterlab-pyhealth

Develops, tests, and validates clinical machine learning models with the PyHealth 2.x healthcare AI toolkit. Use when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, length of stay, drug recommendation), medical coding systems (ICD, NDC, ATC, CCS), physiological signals…

AlterLab-IEU/AlterLab-Academic-Skills · 132 tokens