Individual skill
stress-testing-agent-changes
Attacks your own agent change, tool grant, dependency, model, or release on purpose, across risk types such as prompt injection, gaining extra power, unsafe output, and tool misuse, and records what you tried, what happened, and the leftover risk. Use when a change widens an agent's power, data access, or network reach before release. Do not use for a typo fix with no agent power involved, or to produce a certified penetration test or formal security audit.
skills/stress-testing-agent-changes/SKILL.md
Source commit e44af0e5811e11a3601625cf657d257915689deb
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Local scripts
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 33
- Repository last updated
- Nov 6, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-safety Repository topic
- coding-agents Repository topic
- configuration-management Repository topic
- developer-tools Repository topic
- prompt-engineering Repository topic
- software-engineering Repository topic
- security Derived category
- testing Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# 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`/`exposed` result with expected behavior written before the result, no finding quietly dropped, and `python 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 in `verification.md` (or `red-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`; an `exposed` finding touching credentials, production data, or users escalates.
