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/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/commands/flyfission/nuclear-grade-context-engineering/ng-turnover)<a href="https://agentmods.dev/commands/flyfission/nuclear-grade-context-engineering/ng-turnover"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-turnover/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/flyfission/nuclear-grade-context-engineering/ng-turnover"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-turnover.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.00000 | $0.00607 |
| Opus 5.5 | $0.00000 | $0.00243 |
| Sonnet 5.5 | $0.00000 | $0.00121 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
ng-turnover 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ng-turnover
Portable command prompt generated from skills/handing-off-work/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
Hands off unfinished work with a closed-loop briefing of state, changed conditions, remaining scope, authority limits, and open evidence. Use when AI-agent, reviewer, verifier, releaser, or resumed-thread work transfers to a new owner. Do not use when the same owner continues uninterrupted with full context.
Use when
- 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.
Do not use when
- 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.
Prompt text
Create a Nuclear-grade turnover record.
Inputs:
- packet:
- current phase:
- outgoing owner / role:
- incoming owner / role:
- last completed action:
- completed artifacts:
- changed conditions:
- remaining work:
- allowed files/commands/tools:
- forbidden files/commands/tools:
- proof still needed:
- stop or hold conditions:
Produce a short turnover record. Include the critical next action, the likely error, the control, the evidence, and a prompt for the incoming owner to confirm they have it and understand it before they act.
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 · 59 lines · 0 tokens per session scan A 03d6a8bef12b
ng-turnover is a command published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 607 tokens. 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 commands, from other repositories
coder-eval-implement-plan
Implement an approved codereval plan phase by phase with risk-scaled per-phase review, then a final code review.
capture-feedback
Quick feedback capture with structured signals.
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
milestone-list
PitWay: List every milestone with a concise one-line status.
bet
Lock a shaped Shape-Up pitch as a bet for the next cycle.