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-what-to-control)<a href="https://agentmods.dev/commands/flyfission/nuclear-grade-context-engineering/ng-what-to-control"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-what-to-control.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.00499 |
| Opus 5 | $0.00000 | $0.00249 |
| Sonnet 5 | $0.00000 | $0.00100 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
ng-what-to-control 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ng-what-to-control
Portable command prompt generated from skills/choosing-what-to-control/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
Decides which code, prompts, models, tools, dependencies, docs, tests, evals, releases, or claims need their approved state tracked. Use when scoping what a change puts at risk or what must stay reviewable. Do not use for scratch work that nothing else depends on.
Use when
- A change touches prompts, models, tools, dependencies, public docs, checkers, templates, skills, commands, release files, or runbooks.
- A reviewer needs to know which state is approved and which kind of drift would matter.
- Agent power or wording about where ideas came from changes.
- Work could hit the wrong target, so the exact item needs to be named before anyone acts.
Do not use when
- The change is local, easy to undo, and holds no state that carries trust.
- The item is already listed in a fresh
controlled-items.mdand the scope has not changed.
Inputs
- The user request, issue, pull request, diff, or change record.
docs/02-operating-system/controlled-items.md.- Any existing
risk.md,basis.md, andplan.md.
Prompt text
List the items this change must keep under control (CM).
Inputs:
- change:
- packet:
- affected files/items:
Return a short table. For each item, give: the item, its type, its current state, its intended state, why it is controlled, a link to its evidence (or the gap), its owner, and what should trigger a re-check. Do not list unrelated repo files. Do not imply formal assurance or compliance.
Verification
- Each controlled item has a reason it is controlled.
- Each item links to evidence or to a stated gap.
- A reviewer can tell which items are in and which are out.
Full skill
For the overview, process, outputs, escalation, common rationalizations, red flags, and source lineage, see skills/choosing-what-to-control/SKILL.md. This command sets up evidence for engineering review; it does not create compliance, formal V&V, safety, security, certification, or regulatory adequacy (see DISCLAIMER.md).
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 · 45 lines · 0 tokens per session scan A 7109d6971bfb
ng-what-to-control 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 499 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
capture-feedback
Quick feedback capture with structured signals.
verification-repair
PitWay: Bounded, approve-before-edit correction after every task is done.
usage-add
PitWay: Accumulate measured planning or qa token usage onto a milestone.
milestone-status
PitWay: Show a milestone's status, contract, progress, and tasks.
task-discard
PitWay: Abandon a dispatched task's worktree without integrating.
plan
Plan a task with scope contract and confidence check.