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 recording-a-known-good-versiongit 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/recording-a-known-good-version)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/recording-a-known-good-version"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/recording-a-known-good-version/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/recording-a-known-good-version"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/recording-a-known-good-version.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.00087 | $0.01037 |
| Opus 5 | $0.00044 | $0.00518 |
| Sonnet 5 | $0.00017 | $0.00207 |
| Haiku 4.5 | $0.00009 | $0.00104 |
Grade A, and why
recording-a-known-good-version 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 11d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Recording a Known-Good Version
Overview
A baseline is simply the version everyone agreed is correct and wants to protect. This skill writes down that version, the evidence that backs it, and the things that would make it out of date.
Decision contract
- Claim checked: the accepted version can be rebuilt exactly from its named commit/PR/release, everything under control is either included or deliberately left out, the accepted residual risks have owners, and the triggers that force a new known-good version are recorded.
- Artifact observed:
controlled-items.md,change-impact.md,verification.md, theship.mddecision, and the identifying commit/PR/release -> abaseline.mdwith included/excluded scope, accepted gaps, and re-record triggers. - Decision affected: warn -- the accepted baseline the ship decision produced, and the triggers that invalidate it.
- Failure class: unrebuildable-baseline (a version recorded as accepted with missing evidence or silently dropped scope).
- Next action: record the missing link or excluded scope as a named gap; escalate when the version affects customers, regulated work, or outside trust.
When to Use
- 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.
When Not to Use
- 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.
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.
- 11d ago First seen · 94 lines · 87 tokens per session scan A 7392e3fb0195
recording-a-known-good-version is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 1,037 once invoked, about $0.0004 per session on Opus 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
agentplane-release-and-packaging-operator
Use when preparing, validating, publishing, auditing, or recovering an Agentplane release, especially package build ordering, version parity, npm/GitHub/GHCR/external distribution publication, public install smoke tests, hosted publish evidence, or release CI failures.
agentplane-task-closure-recovery
Use when Agentplane task completion, direct finish, branchpr integration, hosted-close, close-tail PRs, PR metadata, dirty task artifacts, or remote branch divergence need diagnosis or recovery.
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
agentplane
Use when a repository uses AgentPlane or the user wants a governed git-native workflow for planning, task execution, verification, and closure.
brpr
(devtools plugin) Create a branch, commit changes, push, and open a PR — or just commit+push+PR if already on a feature branch. Links related issues from GitHub or Linear based on project tracker config.
merge
Merge or squash-merge a pull request and report best-effort remote and local source-branch cleanup. Use when user says "merge this PR", "squash merge", "md", "smd", or anything about merging pull requests.