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 creating-change-recordsgit 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/creating-change-records)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/creating-change-records"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/creating-change-records.svg" alt="Measured on agentmods" 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.00070 | $0.01342 |
| Opus 5 | $0.00035 | $0.00671 |
| Sonnet 5 | $0.00014 | $0.00268 |
| Haiku 4.5 | $0.00007 | $0.00134 |
Grade A, and why
creating-change-records 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 8d 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.
Creating Change Records
Overview
A change record keeps the whole story in Git, together: the scope, what the change must do, the plan, the trace from claim to evidence, the proof, and the release decision. Use the smallest record that still lets a doubting reviewer decide.
Decision contract
- Claim checked: the record carries every file its mode requires, with the required links, exit criteria, source-lineage notes, and plain status labels (
pass,fail,gap,deferred,not applicable,planned) present and the internal links resolving. - Artifact observed: the mode from
risk.mdand thetemplates/quick/ortemplates/standard/templates -> a Quick record (risk.md,proof.md) or Standard record (risk.md,basis.md,plan.md,trace.md,verification.md,ship.md) plus the validator result. - Decision affected: block -- whether the packet is structurally complete and valid (
python tools/ng.py validatepass/fail). - Failure class: incomplete-record (a missing file, broken internal link, or proof command absent).
- Next action: add the missing file or link and rerun the validator; raise Quick to Standard or human review when proof cannot answer the reviewer.
When to Use
- You are starting a real AI-assisted change.
- You are updating a record after the scope, proof, risk, or release posture changed.
- You are preparing a pull request that needs evidence beyond the usual review notes.
- A preview, a self-check, a handoff, a lesson from operation (OPEX), or a supplier trust check is in play and needs a record.
When Not to Use
- The work leaves no lasting artifact and no need for review.
- The request is only to browse or explain existing docs.
- You only need to pick the mode / grade the change's risk, not author the record yet -- use
rating-change-riskinstead.
Inputs
- The chosen mode from
risk.mdor from the risk-rating skill. - A questioning-attitude screen, when uncertainty, AI power, dependency trust, or release stakes are real.
- Templates under
templates/quick/ortemplates/standard/. - The files the change affects and the proof commands.
- An existing record, if there is one.
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.
- 8d ago First seen · 107 lines · 70 tokens per session scan A 0b2c93bc1e97
creating-change-records is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 2d ago), licensed MIT. It adds 70 tokens to every session and 1,342 once invoked, about $0.0003 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.
coding-agents-farm
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
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.
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.