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 agentmods add commands/flyfission/nuclear-grade-context-engineering/ng-baselinegit 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-baseline)<a href="https://agentmods.dev/commands/flyfission/nuclear-grade-context-engineering/ng-baseline"><img src="https://agentmods.dev/badge/commands/flyfission/nuclear-grade-context-engineering/ng-baseline.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 | $0.00000 | $0.00557 |
| Opus 5 | $0.00000 | $0.00279 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
ng-baseline 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 4d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ng-baseline
Portable command prompt generated from skills/recording-a-known-good-version/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.
Records the version everyone agreed is correct, the evidence behind it, and what would make that record out of date. Use when a standard change ships, when prompts, models, tools, dependencies, docs, or release items are accepted, or when a lesson forces a re-record. Do not use for a tiny local edit with nothing to release or trust, or while the work is still under review.
Use when
- A standard change ships, or the public-facing state of the workflow changes.
- Controlled prompts, models, tools, dependencies, docs, templates, skills, commands, checkers, or release items are accepted.
- A lesson from operation or a piece of review feedback means you need to re-record the known-good version.
- A near miss or operating lesson changes the accepted state or the trigger for re-checking it.
Do not use when
- The change is a tiny local edit with nothing to release and no trust on the line.
- The work is still under review and the evidence is not ready.
Inputs
- The records for what is under control, the ripple effects, the verification, and the ship decision (
controlled-items.md,change-impact.md,verification.md, andship.md). - The pull request, commit, or release that identifies the exact version.
- The gaps you accepted and the triggers for re-checking.
Prompt text
Create or update the Nuclear-grade baseline record for this change.
Inputs:
- packet:
- baseline identity:
- included controlled items:
- excluded items/claims:
- verification evidence:
- OPEX / near-miss links:
- accepted gaps:
Return a baseline record. Include the version that is saved, the items it covers, the items it leaves out, links to the evidence, the gaps you have accepted, and what should trigger a re-check or a new baseline. Do not imply formal assurance or compliance.
Verification
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.
- 4d ago First seen · 49 lines · 0 tokens per session scan A 6888201f80ed
ng-baseline is a command published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 557 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
check-gates
Run a Pre-Action Gate check against prevention rules before executing a risky action.
task-verify
PitWay: Run an inprogress task's approved verification command and persist evidence.
fix
Universal debugging and fix application with semantic code analysis.
domain-research
Conduct domain research covering industry analysis, regulations, technology trends, and ecosystem dynamics using current web data and verified sources.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.
editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.