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 FlyFission/nuclear-grade-context-engineering --skill choosing-what-to-controlgit 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/choosing-what-to-control)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/choosing-what-to-control"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/choosing-what-to-control/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/flyfission/nuclear-grade-context-engineering/choosing-what-to-control"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/choosing-what-to-control.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.00066 | $0.01083 |
| Opus 5.5 | $0.00026 | $0.00433 |
| Sonnet 5.5 | $0.00013 | $0.00217 |
| Haiku 4.5 | $0.00007 | $0.00108 |
Grade A, and why
choosing-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 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Choosing What to Control
Overview
Controlled items are the parts of a system whose approved version matters. They matter to trust, to review, to being able to repeat a result, to what an agent may do, or to a release. This skill keeps the approved version of those items under control. Engineers call that keeping the approved version under control, or configuration management (CM).
Decision contract
- Claim checked: every item whose approved state affects trust, agent power, the release, repeatability, or public understanding is named -- with owner, current and intended state, an evidence link or stated gap, and a re-check trigger -- and nothing in scope is silently left uncontrolled.
- Artifact observed: the request/diff/record and
controlled-items.md(plus anyrisk.md,basis.md,plan.md) -> the controlled-item list with owners, states, triggers, and named gaps. - Decision affected: warn -- which code, prompts, models, dependencies, docs, and releases become controlled items (feeds
change-impact.mdand the baseline). - Failure class: uncontrolled-item (drift in an unlisted prompt, doc, or agent-power state left untracked).
- Next action: name the item, owner, and re-check trigger; escalate when drift could hit users, security, releases, or agent power.
When to Use
- 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.
When Not to Use
- 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.
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 · 90 lines · 66 tokens per session scan A 6d9f6a1eb64b
choosing-what-to-control is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It adds 66 tokens to every session and 1,083 once invoked, about $0.0003 per session on Opus 5.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
contextlock
Safely inspect a repository through the ContextLock MCP server. Use when exploring, searching, reviewing, or auditing repository files with ContextLock, especially before reading unfamiliar code or when sensitive files and secrets may be present.
parabricks
Plan NVIDIA Parabricks pbrun commands, translate CPU options and check runtime readiness. Use for individual tools, including planning-only questions.
jetson-diagnostic
Read-only Jetson health snapshot for identity, memory, GPU, thermal, power, storage, services, and top processes.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
holoscan-install-wheel
Install Holoscan SDK 5.x CUDA 13 Python wheels in an isolated environment, choosing the full stack or version-matched components.
doca-socket-relay
Use this skill when the operator is driving the DOCA Socket Relay to bridge a socket-oriented host application onto a BlueField DPU peer without rewriting it — picking the deployment shape (in-process, sidecar, or BlueField service container), configuring the host-side socket and the DPU-side forwarding endpoint…