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/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/creating-change-records"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/creating-change-records.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.00070 | $0.01342 |
| Opus 5.5 | $0.00028 | $0.00537 |
| Sonnet 5.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 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.
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.
- 1mo 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 3d ago), licensed MIT. It adds 70 tokens to every session and 1,342 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
remember
Save the decisions, facts, dead ends and architecture this conversation established to Atlas's shared memory, so other agents and future sessions can build on them.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
pr-explainer
Use when a developer asks to explain a pushed PR, walk through a PR stack, understand one stack member, or explain what an AI agent just pushed so they can connect code changes to end-to-end functionality and update domain knowledge. Not for defect review, merge approval, PR-body authoring, or full-repository…
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".
ci-cd-pipeline-authoring
Use when a repository needs CI/CD - author GitHub Actions workflows so TaskTrooper's pipeline auto-detects your validate/build/test jobs and stage/preprod/prod deploys, and so a dispatch delivery profile can dispatch the production deploy.
stepwise-task-execution
Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a needrevision bounce.