Borrowing it
Nothing to install: this file belongs to mick-gsk/drift. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mick-gsk/drift/main/.github/skills/drift-session-handover-authoring/SKILL.mdgit clone --depth 1 https://github.com/mick-gsk/driftWrote 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/mick-gsk/drift/drift-session-handover-authoring)<a href="https://agentmods.dev/skills/mick-gsk/drift/drift-session-handover-authoring"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-session-handover-authoring/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/mick-gsk/drift/drift-session-handover-authoring"><img src="https://agentmods.dev/badge/skills/mick-gsk/drift/drift-session-handover-authoring.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.00096 | $0.01635 |
| Opus 5 | $0.00048 | $0.00817 |
| Sonnet 5 | $0.00019 | $0.00327 |
| Haiku 4.5 | $0.00010 | $0.00163 |
Grade A, and why
drift-session-handover-authoring 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 10d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drift Session Handover Authoring
Use this skill when you are about to call drift_session_end and must produce
the handover artifacts required by ADR-079 and the session-handover contract in
.github/prompts/_partials/session-handover-contract.md.
When To Use
- You touched files under
src/drift/during the session. - You completed one or more fix-plan tasks.
- You ran multiple scans / diffs / nudges and want to hand off to the next agent (or to the maintainer).
drift_session_endreturnedDRIFT-6100and you need to fill the missing artifacts.
When Not To Use
- Empty sessions (no tool calls beyond session start, no completed tasks, no touched files). The gate auto-exempts them.
- Pure read-only exploration that touched no code.
Core Rules
- Agent writes, server validates. You author the artifacts. The MCP server only checks existence, shape, placeholders (and optionally runs an LLM review). Do not try to satisfy the gate with generated filler.
- No placeholder tokens.
TODO,FIXME,XXX,TBD,???,<N>,<NNN>,LOREM,IPSUM,FOO,BAR,BAZoutside of ≥5-line code fences block the gate at L3. - Cross-check session id. The
session_idin the Markdown frontmatter must match the active session exactly. - SIGNAL / ARCHITECTURE classes require all three artifacts. Evidence JSON, ADR draft, and session markdown.
force=trueis a last resort. It requires an auditablebypass_reasonof at least 40 characters without placeholder tokens, and it is logged and persisted in the session trace.
Step 1: Policy Gate
Before writing artifacts, run the mandatory gate from
.github/instructions/drift-policy.instructions.md. If the underlying change
is inadmissible the gate blocks you here, not at drift_session_end.
Step 2: Determine Your Change Class
Ask yourself what the session actually changed:
| Touched paths | Class | Required artifacts |
|---|---|---|
src/drift/signals/** or src/drift/scoring/** |
signal |
evidence + ADR + session_md |
src/drift/ingestion/**, output/**, api/**, mcp_*, session* |
architecture |
evidence + ADR + session_md |
Other src/drift/** |
fix |
session_md |
docs/**, docs-site/**, .github/prompts/**, skills, instructions |
docs |
session_md |
| Only config, lockfiles, CI, tasks.json | chore |
session_md |
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.
- 10d ago First seen · 165 lines · 96 tokens per session scan A 180df80a229d
drift-session-handover-authoring is a skill published in the GitHub repository mick-gsk/drift (15 stars, last pushed 1mo ago), licensed MIT. It adds 96 tokens to every session and 1,635 once invoked, about $0.0005 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
dispatcher
Use this skill when running a Taniwha build from the main Claude Code session. The skill turns the main session into a thin, mechanical executor that follows instructions from ephemeral orchestrator subagents. Trigger this whenever the user wants to start a Taniwha build, resume an interrupted one, or work on a…
contract-derivation
Use this skill after a design document exists and before any module is implemented. It takes a design doc and derives per-module contracts (manifests) that are complete enough for an implementor working in isolation to build each module correctly without seeing the rest of the system. Trigger this whenever the user…
design-doc
Use this skill before writing any non-trivial code, especially when starting a new feature, service, or codebase. It produces a structural design document that commits to module boundaries, contracts, and data shapes BEFORE implementation begins. Trigger this whenever the user describes building something new, asks to…
verifier
Use this skill when verifying that a completed Taniwha implementation or composition satisfies its contract's acceptance criteria. The verifier reads the contract, the implementation's source files, and the project context, then writes its own tests against the contract's acceptance criteria, runs them, and reports…
composition
Use this skill when wiring two completed modules together to satisfy a parent contract, especially in a compartmentalised setting. Trigger this whenever the user has two implemented modules (each with its manifest) and a parent contract that says how they should compose, when the user asks to "compose these modules"…
leaf-implementation
Use this skill when implementing a single module against a contract manifest, especially in a compartmentalised setting where the implementor should NOT see the rest of the system. Trigger this whenever a manifest exists and the user wants to implement that module, asks to "implement this module", "build against this…