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 double-checking-before-actinggit 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/double-checking-before-acting)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/double-checking-before-acting"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/double-checking-before-acting/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/double-checking-before-acting"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/double-checking-before-acting.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.00078 | $0.01123 |
| Opus 5.5 | $0.00031 | $0.00449 |
| Sonnet 5.5 | $0.00016 | $0.00225 |
| Haiku 4.5 | $0.00008 | $0.00112 |
Grade A, and why
double-checking-before-acting 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Double-Checking Before Acting
Overview
A self-check turns a high-stakes action into a careful one. Before you claim success, name the target, the result you expect, when to stop, the action itself, and the check you will run afterward.
Decision contract
- Claim checked: the target, expected result, and stop condition were named before the action, and the real result was compared against the expected one before claiming success.
- Artifact observed: the proposed action, target, and authority -> a
self-check.mdnote of action, target, expected/real result, stop condition, evidence, and any mismatch. - Decision affected: block -- whether to proceed with or abort the critical action: a big edit, command, public claim, trust change, or release.
- Failure class: wrong-target-or-unverified-action (acting on an assumed target, or claiming success without comparing the result).
- Next action: pause and escalate when authority, target, or evidence is unclear; a mismatch halts the action rather than triggering a retry.
When to Use
- A command can delete, move, publish, release, migrate, or change something outside the repo.
- An edit touches public claims, where ideas came from, permissions, credentials, dependencies, models, APIs, or the release.
- An agent is about to make a wide or repeated change, where hitting the wrong target is easy.
- A quick candidate is about to become a public claim, an accepted version, or a release action.
When Not to Use
- The task is a tiny local edit with obvious proof.
- The action only reads data and has no effect on any later decision.
- The change record already requires a stronger human check before the action.
Inputs
- The action you mean to take, the exact target, the current phase, and where your authority comes from.
- The result you expect, the most likely wrong-target mistake, and when to stop.
- The proof command, review check, or evidence link you will need after the action.
Process
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 · 107 lines · 78 tokens per session scan A 0d99e3e2e04b
double-checking-before-acting is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 1,123 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…