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 agentmods add skills/fmind/dot/handovernpx skills add fmind/dot --skill handovergit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/handover)<a href="https://agentmods.dev/skills/fmind/dot/handover"><img src="https://agentmods.dev/badge/skills/fmind/dot/handover.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 | $0.00033 | $0.00829 |
| Opus 5 | $0.00016 | $0.00415 |
| Sonnet 5 | $0.00007 | $0.00166 |
| Haiku 4.5 | $0.00003 | $0.00083 |
Grade A, and why
handover 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 yesterday.
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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handover
Turn everything this session established into one prompt a fresh agent can execute without asking a question. In the same harness, prefer --continue, --resume, or /compact; this skill is for a fresh or different harness. Writing a handover is a documentation act: produce the prompt file and stop, because the next session owns execution.
Workflow
- Re-read the session: recover the original request, every subsequent user correction, and the decisions each one settled. A later correction overrides an earlier instruction; carry the resolved position, not the debate.
- Separate instruction from inference: mark what the user required, what you proposed and they approved, and what you assumed without confirmation. The next agent must know which lines it may revise.
- Verify before you write: re-check every path, symbol, command, and version the prompt will name. Stale coordinates send the next session confidently to the wrong place; drop or re-derive anything you cannot confirm now.
- Capture the position: completed work with its proof, in-progress work with its exact stopping point, and untouched work. Name the branch and whether the tree is clean.
- Record the trade-offs: for each real decision, the choice, the alternatives, and why; for each dead end, what failed and how, so the next session does not retry it.
- State the proof contract: the commands that must pass before the work is done (normally
mise run checkandmise run test) and any check that is currently red. - Draft as an instruction, not a report: address the receiving agent in the imperative; it needs orders and context, not a narrative of what you did.
- Test for self-containment: read the draft as someone who never saw this session. Every pronoun must resolve, every "as discussed" becomes the substance, every file reference is a path.
- Write the file:
.agents/prompts/<YYYY-MM-DD>-<slug>.mdundergit rev-parse --show-toplevel(or~/.agents/prompts/outside a repository) using the prompt template; create the directory if missing and report the path.
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.
- yesterday First seen · 38 lines · 33 tokens per session scan A 3e67c35fe86c
handover is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 829 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.