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-ship-review)<a href="https://agentmods.dev/commands/flyfission/nuclear-grade-context-engineering/ng-ship-review"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-ship-review.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.00000 | $0.00632 |
| Opus 5 | $0.00000 | $0.00316 |
| Sonnet 5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
ng-ship-review 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 8d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ng-ship-review
Portable command prompt generated from skills/checking-release-readiness/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
Records a ship, block, defer, or ship-with-risk decision that ties baseline, evidence status, residual risk, rollback, monitoring, and handoff together. Use when a packet, PR, release, dependency change, or agent-authority change approaches merge. Do not use early in development before evidence exists.
Use when
- A Standard change record is getting close to merge or release.
- A pull request changes how users see the system, its security, its dependencies, what an agent may do, or how it runs in production.
- Evidence gaps have to be accepted or made into blockers.
- A quick candidate is being promoted into a baseline, a public claim, a release, or any other state that carries trust.
- A handoff, a support handoff, a lesson from real operation (OPEX), or a cautious decision stance needs to be stated plainly.
Do not use when
- The work is a local Quick change record with no effect on a release.
- An incident is still being contained or rolled back.
Inputs
ship.md,verification.md,trace.md, the pull request status, the CI status, the rollback plan, the monitoring plan, and the open risks.docs/02-operating-system/change-control-packets.md.
Prompt text
Perform a Nuclear-grade ship-readiness review.
Inputs:
- packet: .nuclear/changes/<slug>/
- baseline: <commit/PR/release>
- evidence status: <summary>
- unresolved gaps: <list>
- rollback/restore path: <summary>
- monitoring/post-release checks: <summary>
- turnover/support handoff:
- OPEX trigger:
Return:
- the release decision: ship, block, defer, or ship with a named leftover risk
- whether the evidence actually answers the decision question
- the evidence custody record and five-axis coupling profile, the consequence-specific minimum, and any residual coupling or blocker
- an evidence summary
- the leftover risks and who owns them
- the rollback and monitoring notes
- why this is the cautious call, the abort trigger, the handoff, and the lessons-from-operation (OPEX) trigger
- the exact packet updates needed
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.
- 8d ago First seen · 60 lines · 0 tokens per session scan A 03b74161a044
ng-ship-review is a command published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 632 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
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
task-dispatch
PitWay: Prepare a parallel-eligible task for worktree execution.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
task-discard
PitWay: Abandon a dispatched task's worktree without integrating.
finish-branch-execute
Step 4 of finishing-a-development-branch: Execute chosen integration option (merge, PR, PR+dance, keep, or discard).
ship
Deliver completed work with validation and documentation.