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 flonat/flonat-research --skill handoffgit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/handoff)<a href="https://agentmods.dev/skills/flonat/flonat-research/handoff"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/handoff/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/flonat/flonat-research/handoff"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00051 | $0.00737 |
| Opus 5 | $0.00026 | $0.00368 |
| Sonnet 5 | $0.00010 | $0.00147 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
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 5d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Handoff
Use one client-neutral handshake for every route. Before acting, read ../shared/cross-client-handoff.md completely and follow its schema and state machine.
Choose the route
- If the user names Claude or Codex, use that client as
to. - If the user asks for the next or a fresh session without naming a client, set
toto the current client. This is the default for Claude-to-Claude and Codex-to-Codex continuation. - Use
to: eitheronly when the task is deliberately client-agnostic. - Set
fromto the current client, orhumanwhen invoked outside a client session.
All routes write <project-root>/.context/ai-handoff.md. Do not create a separate client-specific handoff file.
Prepare a handoff
- Resolve the project root from the current working directory or the named project.
- Read only the relevant durable guidance and state:
CLAUDE.md,AGENTS.md, the latest approved plan, current focus, recent log, and any existing handshake. Never inspect restricteddata/raw/content. - Use the supplied outcome. If none is supplied, infer the highest-priority open loop; ask only if different choices would materially change scope.
- Reconcile the existing handshake. Preserve still-valid decisions and its log, then create a new
handoff_idand setstatus: ready. - Record the source and target client, source and target machine, branch, commit, exact working-tree ownership, observable acceptance criteria, real commands, and the first concrete action.
- Validate the YAML frontmatter and Markdown sections against the shared protocol. Check that the file contains no secrets, credentials, transcripts, caches, or restricted data.
Never overwrite project-owned CLAUDE.md or AGENTS.md: they remain durable client guidance. Never auto-commit or push the handshake.
Receive a handoff
When .context/ai-handoff.md targets the current client or either:
- Read both native guidance files and the handshake before editing.
- Compare the recorded branch, commit, machine, and changed-file ownership with the actual working tree.
- Set
status: acceptedand append a timestamped log entry before substantive work. - Set
status: in_progresswhen execution begins. - Maintain acceptance criteria and the log. Finish with
complete, or useblockedwith the precise blocker and safe next action.
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.
- 5d ago First seen · 51 lines · 51 tokens per session scan A aa9150cbf364
handoff is a skill published in the GitHub repository flonat/flonat-research (132 stars, last pushed 14d ago), licensed MIT. It adds 51 tokens to every session and 737 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-09-03.
Other skills, from other repositories
buffer-sizing
Calculate project, feeding, and resource buffers — shared with implementation-planning.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
speckit-companion-specify
../../../.specify/extensions/companion/.specify-dev/agent-commands/claude/speckit-companion-specify/SKILL.md.