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-prove)<a href="https://agentmods.dev/commands/flyfission/nuclear-grade-context-engineering/ng-prove"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-prove/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-prove"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-prove.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.00659 |
| Opus 5.5 | $0.00000 | $0.00264 |
| Sonnet 5.5 | $0.00000 | $0.00132 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
ng-prove 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ng-prove
Portable command prompt generated from skills/proving-claims/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
Builds claim-to-evidence trace rows with statuses, gaps, tests, evals, reviews, and narrower non-claims. Use when a packet asserts something a reviewer must trust. Do not use to make the final ship decision, judge public legal wording, or invent evidence that does not exist.
Use when
- A change record makes claims about the code, says something about safety or security, claims release readiness, or claims a dependency can be trusted.
- Tests pass, but reviewers cannot see which claim each test backs up.
- Evidence gaps have to be accepted, put off, or treated as blockers.
- The proof needs the right kind of check. The kinds are self-check, peer-check, concurrent verification (a second person checks as you go), independent verification (a separate person checks afterward), peer review, a test, or an eval.
Do not use when
- The request is to make the final ship/defer/block decision; use
checking-release-readinessafter the trace is built. - The request is to judge public legal, safety, security, certification, or compliance wording; use
checking-legal-and-safety-wording. - The request is to validate citation lineage or source authority; use
checking-source-claims.
Inputs
basis.md,trace.md,verification.md, andship.md.- Test commands, CI runs, reviews, logs, diffs, screenshots, and source links.
- Known gaps and leftover risks.
Prompt text
Prove the important Nuclear-grade claims in this packet.
Inputs:
- packet: .nuclear/changes/<slug>/
- claims: <list or source file>
- evidence available: <commands/links/reviews/logs>
- known gaps: <list>
Return:
- claim -> basis -> control/design feature -> support type -> verification type -> evidence -> status -> ship posture
- for each load-bearing claim: evidence custody (generated, selected, transformed/summarized, executed/captured, retained, presented)
- the five-axis actor–evidence coupling profile (actor, context, mechanism, authority, resource), the consequence-specific minimum, and any residual coupling or blocker
- narrower wording for any claim that is too broad
- the gaps, deferrals, or blockers, stated plainly
- the validator command to run
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 · 55 lines · 0 tokens per session scan A cc62d9d868f5
ng-prove 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 659 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
generate-and-verify
Trigger annotation processing in the demo module to generate all outputs (DTOs, MCP tools, REST controllers, OpenAPI spec), then verify the generated code compiles and matches expected patterns. List all generated files with a summary of what each contains.
build
Full build and verification.
verify
Run the required checks (format, typecheck, lint, test, build) and report the results.
generate-tests
Generate tests for changed files — unit tests for functions, integration tests for APIs, E2E for user flows.
red-team
Red-team your safety scanning by generating adversarial variants of a prompt injection attempt.
checklist
Generate a custom checklist for the current feature based on user requirements.