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.
git clone --depth 1 https://github.com/FlorinI/Florians-Claude-Code-KitWrote 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/commands/florini/florians-claude-code-kit/handover)<a href="https://agentmods.dev/commands/florini/florians-claude-code-kit/handover"><img src="https://agentmods.dev/badge/commands/florini/florians-claude-code-kit/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/commands/florini/florians-claude-code-kit/handover"><img src="https://agentmods.dev/badge/commands/florini/florians-claude-code-kit/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.00083 | $0.03960 |
| Opus 5.5 | $0.00033 | $0.01584 |
| Sonnet 5.5 | $0.00017 | $0.00792 |
| Haiku 4.5 | $0.00008 | $0.00396 |
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 25d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/handover — deliberate session handover
You are about to do a clean session handover. Don't /clear yet; the user will do that after the handover file is written.
Invocation — /handover vs /handover ok
If the command was invoked with the argument ok (case-insensitive — ok, OK, Ok all count), run the flow with the proposed default buckets and no confirmation prompt — but NOT silently. Specifically, in this order:
- Draft the eight coordinates (Step 1) internally. You do not need to print the long-form draft.
- Print the Step-2 triage summary table — the compact
N. [bucket] itemlist, defaults already filled in, in the exact format the interactive flow uses (see Step 2). Show it BEFORE acting on or writing anything. This is the recap the user reacts to: because it lands before any M/D/X action or file write, the user can scan it and hit Esc to interrupt and correct course if a bucket is wrong. - Do NOT pause for triage adjustments and do NOT ask for confirmation. After printing the table, continue straight on in the same turn — act on the M, D, and X items (Step 3), write the handover file (Step 4), and report (Step 5).
The only pauses still permitted are the deliberate-action confirmations in Step 3 for outward-facing or hard-to-reverse X items (commits, pushes, deletes, sends) — those are never auto-run off defaults.
Otherwise (plain /handover), run the full interactive flow below: present the draft, take the user's triage adjustments, then act.
The intent note — any other text in the arguments
Everything in the arguments except a leading ok is the intent note: the user's message to the session that picks this handover up — why they are stopping and what they plan to do next. No keyword introduces it, and quotes are optional (strip one pair of surrounding quotes if present).
| Invocation | Mode | Intent note |
|---|---|---|
/handover ok I'll get back to this on my other computer. |
non-interactive | I'll get back to this on my other computer. |
/handover This is step two of five; the plan lives in another repo. |
interactive | the whole argument |
/handover ok or /handover |
as above | none |
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.
- 25d ago Changed · +27 lines · +22 tokens per session 79005d6ff502
- 1mo ago Changed · +4 lines 68a8ee2228f3
- 1mo ago First seen · 184 lines · 61 tokens per session scan A 1eeddb7f4182
handover is a command published in the GitHub repository FlorinI/Florians-Claude-Code-Kit (5 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 3,960 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-31.
Other commands, from other repositories
okf
Bundle de connaissance OKF dans okf/ : source de vérité (architecture, vision, marketing, roadmap, conventions). Cette commande aiguille vers le bon usage selon $ARGUMENTS.
context-audit.template
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows.
remember
Save the user's input into Tau Git Memory now.
tree
Show the Tau Git Memory tree as a visual schema.
recall
Search Tau Git Memory now for.
status
Run Tau Git Memory status now.