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 stress-testing-agent-changesgit 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/stress-testing-agent-changes)<a href="https://agentmods.dev/skills/flyfission/nuclear-grade-context-engineering/stress-testing-agent-changes"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/stress-testing-agent-changes/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/stress-testing-agent-changes"><img src="https://agentmods.dev/badge/skills/flyfission/nuclear-grade-context-engineering/stress-testing-agent-changes.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.00103 | $0.01825 |
| Opus 5.5 | $0.00041 | $0.00730 |
| Sonnet 5.5 | $0.00021 | $0.00365 |
| Haiku 4.5 | $0.00010 | $0.00183 |
Grade A, and why
stress-testing-agent-changes 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stress-Testing Agent Changes
Overview
When an agent can use tools, read data, or affect releases, it gives attackers something to aim at. Normal "does it work" testing does not test for that. This skill is about attacking your own work on purpose to find weak spots (red teaming). You do it in an orderly way: list the kinds of attacks that matter here, say what safe behavior should look like, try the attacks (or simulate them), write down what happened, and tie the findings into the packet's evidence record.
Decision contract
- Claim checked: each attack type chosen for this setup has a recorded
contained/uncertain/exposedresult with expected behavior written before the result, no finding quietly dropped, andpython tools/ng.py validate .nuclear/changes/<slug>passes. - Artifact observed:
basis.md,risk.md, and past OPEX records naming the agent role, tools, and data reach -> a red-team record inverification.md(orred-team.md) with each type's result, leftover risk, and backup controls. - Decision affected: block -- per adversarial class, contained / uncertain / exposed; uncertain or exposed findings feed
ship.md. - Failure class: unhardened-agent-power (an unchecked attack type, or an exposed finding shipped with no named leftover risk).
- Next action: name leftover risk and backup controls in
ship.md; anexposedfinding touching credentials, production data, or users escalates.
When to Use
- An agent is getting new tools, network access, credentials, or the power to write files.
- A change widens what an agent may read, run, call, or release.
- A dependency or model update may change how the agent handles input it should not trust.
- The release packet needs attack evidence, not just "does it work" test coverage.
- A past OPEX record (a lessons-from-operation record) found a gap in how attacks were handled.
When Not to Use
- The change involves no agent power (it is pure data, formatting, or documentation work).
- A formal penetration test, certified security audit, or regulatory exercise is already planned.
- The packet mode is Quick and the risk check confirms no new trust or permission boundary.
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 · 124 lines · 103 tokens per session scan A aa802c1dc878
stress-testing-agent-changes is a skill published in the GitHub repository FlyFission/nuclear-grade-context-engineering (33 stars, last pushed 3d ago), licensed MIT. It adds 103 tokens to every session and 1,825 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
nemo-automodel-recipe-development
Create and modify NeMo AutoModel training and evaluation recipes, including YAML structure, builders, and execution flow.
mcore-testing
Test system for Megatron-LM. Covers test layout, recipe YAML structure, adding and running unit and functional tests, golden values, marker filters, and CI parity.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
playwright-skill
Complete browser automation with Playwright. Auto-detects dev servers, writes reusable test scripts, and supports screenshots, responsive checks, UX validation, login flows, link checks, and arbitrary browser automation. Use when the user wants to test a website, automate browser interactions, validate web…