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 benjaminard/fable-skills --skill plain-handoffgit clone --depth 1 https://github.com/benjaminard/fable-skillsWrote 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/benjaminard/fable-skills/plain-handoff)<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="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.00063 | $0.00609 |
| Opus 5 | $0.00032 | $0.00304 |
| Sonnet 5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
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 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.
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:
- Open with the outcome. One sentence on what happened or what you found, before any detail.
- Then the one or two things you need from them, each explained as if new.
- 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_TYPEin entrypoint," but "fixed by adding theSCRAPER_TYPEenvironment 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:
- What was the goal? (One clause; the user may be returning after hours.)
- What is the outcome? (Done, partially done, blocked, and on what evidence.)
- What changed? (Files, systems, state, in plain language.)
- What do you need from the user, if anything?
- What did you deliberately not do? (Out-of-scope findings, deferred work, known limitations.)
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.
- 7d ago First seen · 42 lines · 0 tokens per session scan A 717ebffe1f7f
plain-handoff is a skill published in the GitHub repository benjaminard/fable-skills (30 stars, last pushed 2mo ago), licensed MIT. It adds 63 tokens to every session and 609 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-30.
Other skills, from other repositories
guidance
Control LLM output with regex and grammars, guarantee valid JSON/XML/code generation, enforce structured formats, and build multi-step workflows with Guidance - Microsoft Research's constrained generation framework.
alterlab-paper-writer
Drafts and revises academic papers through a 12-agent pipeline with hardened LaTeX output (apa7 document class, justified text, table column-width formula, centered bilingual abstracts, standardized font stack, PDF compiled from LaTeX), supporting IMRaD, literature review, theoretical, case study, policy brief, and…
alterlab-pyhealth
Develops, tests, and deploys clinical machine learning models with the PyHealth healthcare AI toolkit. Use when working with electronic health records (EHR), clinical prediction tasks (mortality, readmission, drug recommendation), medical coding systems (ICD, NDC, ATC), physiological signals (EEG, ECG), healthcare…
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-phylogenetics
Build phylogenetic trees end-to-end from raw sequences — MAFFT multiple sequence alignment, optional TrimAl trimming, IQ-TREE 2 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-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…