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 fmind/dotfiles --skill handovergit clone --depth 1 https://github.com/fmind/dotfilesWrote 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/dotfiles/handover)<a href="https://agentmods.dev/skills/fmind/dotfiles/handover"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/handover/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.
<a href="https://agentmods.dev/skills/fmind/dotfiles/handover"><img src="https://agentmods.dev/badge/skills/fmind/dotfiles/handover.svg" alt="Reviewed on agentmods" width="80" 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.00038 | $0.01372 |
| Opus 5.5 | $0.00015 | $0.00549 |
| Sonnet 5.5 | $0.00008 | $0.00274 |
| Haiku 4.5 | $0.00004 | $0.00137 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 73 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.
Authority Boundary
Writing a handover is a documentation act. Produce the prompt file and stop. Do not implement the work it describes, commit it, or push it unless the user separately asks. The next session owns execution.
What a Handover Carries
The receiving agent starts with an empty context window. It sees the repository and the prompt — nothing else. Four classes of knowledge die with this session unless the prompt captures them:
- User-stated constraints: preferences, rejections, and scope limits the user gave in conversation. These are authoritative and unrecoverable from the code.
- Verified findings: facts confirmed this session by reading dependency source, running a command, or fetching documentation — with the evidence that settled them.
- Rejected alternatives: options considered and dropped, with the reason. Without these the next session re-litigates settled decisions or walks into a known dead end.
- Current position: what is done, what is half-done, and what has not started.
Repository state that the next agent can read for itself is not knowledge — it is noise. Point at files instead of transcribing them.
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 are worse than absent ones — they send the next session confidently to the wrong place. Drop or re-derive anything you cannot confirm now.
- Capture the position: Record 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, state the choice, the alternatives, and why. For each dead end, state what failed and how it failed, so the next session does not retry it.
- State the proof contract: Name 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" must be replaced by the substance, every file reference must be a path. Rewrite anything that only makes sense to you.
- Write the file: Save to
.agents/prompts/<YYYY-MM-DD>-<slug>.mdand report the path so the user can paste or pipe it into the next session.
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.
- 1mo ago First seen · 73 lines · 38 tokens per session scan A df3cbb517998
handover is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,372 once invoked, about $0.0002 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-31.
Other skills, from other repositories
auth-status
Check CLI and ADC logins across providers: expiry, scopes, re-login commands.
gws
Use gws for Google Workspace: Gmail, Drive, Docs, Sheets, Calendar, and Chat.
draft-mail
Draft Gmail emails and replies in the recipient's language; never send.
dprint
Format Markdown, JSON, TOML, and YAML with dprint.
delegate-tasks
Delegate task batches to agy or another harness on explicit request.
mise
Manage mise tool pins, lockfiles, environments, and tasks shared by hooks and CI.