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/flyfission/nuclear-grade-context-engineering/handing-off-worknpx skills add FlyFission/nuclear-grade-context-engineering --skill handing-off-workgit clone --depth 1 https://github.com/FlyFission/nuclear-grade-context-engineeringWrote 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/flyfission/nuclear-grade-context-engineering/handing-off-work)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/handing-off-work"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/handing-off-work.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.1 | $0.00065 | $0.01173 |
| Opus 5 | $0.00032 | $0.00587 |
| Sonnet 5 | $0.00013 | $0.00235 |
| Haiku 4.5 | $0.00006 | $0.00117 |
Grade A, and why
handing-off-work 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 6d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Handing Off Work
Overview
A handoff transfers responsibility, not just context. The next person or agent has to know what changed, what is left, what they are allowed to do, and when to stop.
Decision contract
- Claim checked: the receiving owner can resume without the chat history -- the last finished action, changed conditions, remaining scope, authority limits, open evidence, and stop conditions are all stated -- and the owner has restated scope, authority, proof owed, and when to stop before acting.
- Artifact observed: the change-record path, current phase, mode, the done/changed/assumed/open state, and the authority limits -> a
turnover.mdwith the resume point, what changed, what remains, the next decision gate, and the incoming owner's confirmation. - Decision affected: block -- whether the receiving owner may resume, or must hold and re-question first.
- Failure class: open-loop-handoff (state only implied, or the owner acts before confirming scope and stop conditions).
- Next action: make the incoming owner restate scope, authority, and stop conditions first; escalate when credentials, production data, or release authority are involved.
When to Use
- Another agent, a reviewer, a verifier, a releaser, or a support owner will keep working.
- A long thread is being picked up again after the context changed.
- Work has open evidence, decisions not yet made, or limits on what the owner may do.
- Release work, incident work, or a lesson from real operation (OPEX) has to move to another owner.
When Not to Use
- The work is done and the change record already holds the evidence and the decision.
- A tiny Quick change needs only a diff and a proof note.
- The request is just to summarize a file, with no transfer of responsibility.
- The next owner only needs a focused brief to start or resume, with no open-work state to carry over -- use
briefing-an-agentinstead.
Inputs
- The change-record path, the current phase, and the chosen mode.
- The work that is done, the conditions that changed, the assumptions still in play, and the open gaps.
- Allowed files, commands, and tools; actions that are off limits; the evidence still owed; and when to stop.
- The next owner and their role: reviewer, verifier, or releaser.
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.
- 6d ago First seen · 104 lines · 65 tokens per session scan A 024a48f60001
handing-off-work is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,173 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-08-30.
Other skills, from other repositories
to-goal
Turn an approved spec, agent-ready ticket, tracker frontier, or partially implemented ticket into a verifiable execution goal without re-interviewing the user. Use after to-tickets or triage, before starting a fresh implementation session; use --all only for an explicitly requested cross-ticket goal.
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
trellis-workflow-enhancer
Audit and apply real, project-local Trellis integrations for Matt Pocock and Waza skills, with phase routing, hook injection, durable artifact handoffs, and smoke-test evidence. Use when a user wants to strengthen, compare, modernize, integrate, or debug Trellis with Matt/Waza workflows, especially when skills are…
specgate-work-preparation
Use when preparing a request or existing source documents for SpecGate approval, creating quick SpecGate work, publishing an artifact version, or repairing artifact readiness before implementation.
jira-issue-create
Create one or more Jira issues through acli from user-approved drafts using heading-based Context, Acceptance criteria, and Engineering notes sections. Use only when explicitly invoked to create Jira issues; use jira-issue-refine when requirements still need refinement.
turritopsis-onboarding
Scan and map a software project with the currently installed Agent, design durable project-specific Stages, validate and apply skeletons, retrieve only relevant truth, and maintain evidence-backed knowledge without replaying chats or sending repository evidence to a second LLM. Use when joining, resuming…