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 closing-stale-packetsgit 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/closing-stale-packets)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/closing-stale-packets"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/closing-stale-packets.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.1 | $0.00084 | $0.01976 |
| Opus 5 | $0.00042 | $0.00988 |
| Sonnet 5 | $0.00017 | $0.00395 |
| Haiku 4.5 | $0.00008 | $0.00198 |
Grade A, and why
closing-stale-packets 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 7d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Closing Stale Packets
Overview
A change packet that is started and then abandoned is a quiet integrity problem. It looks like work in progress, but no one owns it, its claims were never proven, and a reader cannot tell whether the change shipped, was dropped, or is still pending. ng status now surfaces these: a scaffold packet is an untouched draft still carrying the placeholder marker; an invalid packet fails validation for another reason. This skill turns that signal into a decision. Every stale packet must reach one honest terminal state: completed (filled and validating), closed (deliberately abandoned with a recorded reason), or deleted (never a real change). The forbidden state is the one most packets drift into: half-done and silent, where a green-looking directory hides an unproven claim. Closing a packet with a written rationale is a first-class successful outcome, not a failure to ship.
Decision contract
- Claim checked: every stale packet reached one honest terminal state -- completed and validating, closed with a recorded reason and decider, or deleted as a genuinely empty scaffold -- none left half-done and silent.
- Artifact observed:
ng status ./validateoutput and the packet against its originating issue/PR/anchor -> aNUCLEAR-GRADE-CLOSED:rationale line and anng status .where every packet isokorclosed. - Decision affected: block -- bring the stale packet to a terminal state so
ng statusreports ok/closed, not scaffold/invalid. - Failure class: silent-stale-packet (a half-done packet hiding an unproven claim, or a faked pass by deleting the marker).
- Next action: complete, close-with-reason, or delete; escalate to the owner before deleting any packet whose change is not confirmed dead.
When to Use
ng statusreports ascaffoldorinvalidpacket and you are deciding what to do about it.- A long or interrupted session left a packet directory behind that was never finished.
- A packet's underlying change was dropped, superseded, or merged elsewhere, but the packet still sits in
.nuclear/changes/. - A periodic cleanup or release-readiness sweep finds packets that do not map to live work.
- A packet was scaffolded to explore an idea that was then abandoned.
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.
- 7d ago First seen · 122 lines · 84 tokens per session scan A 03d4542da24f
closing-stale-packets is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 1,976 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
contextlock
Safely inspect a repository through the ContextLock MCP server. Use when exploring, searching, reviewing, or auditing repository files with ContextLock, especially before reading unfamiliar code or when sensitive files and secrets may be present.
nopus-simplify
Rewrite the immediately preceding assistant response with clearer and more direct prose when the user invokes this skill.
thumbgate-guard
Turn the agent's most recent mistake into an enforced ThumbGate prevention rule (a PreToolUse block gate) so the same bad tool call is intercepted before it runs again, in this and every future session across Claude Code, Cursor, Codex, Gemini, Amp, and Cline. Captures the failure with the capturefeedback MCP tool…
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.
search-lessons
Search promoted lessons for corrective actions, lifecycle state, linked rules, and linked gates.
release
Automate the release process. Use when user says "cut a release", "new version", "bump version", "publish release", or anything about versioning and publishing.