Red-Team Your Agent with Adversarial Prompts
Agent QA & Security
120-180 minutes0/4 steps0%
Step 1 of 4
Build a threat-driven probe set
Attack what matters to this agent, not a generic checklist.
First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.
Prompt Capsule
Define the vulnerability probe set from my agent's threat model. Relevant classes for a tool-using coding agent: prompt injection (direct and indirect), data leakage (secrets, other users' data, system prompt extraction), tool/permission bypass (getting restricted actions to fire), destructive-action induction, jailbreaks of safety refusals, and excessive-agency (agent doing more than asked with real consequences). For each class, note what a successful attack would achieve against MY system specifically (what data, which tools). Prioritize by impact x likelihood. Use a red-teaming framework's probe catalog (e.g. DeepTeam-style vulnerability/attack taxonomies) as a source, but select and adapt to my risks. Deliver the prioritized probe set.
Paste into EmergentFull Build: complete implementation prompt with explicit requirements
Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.
Actual change check
Expected after this step
A prioritized, threat-driven probe set adapted to the agent.
Should NOT happen
- An existing feature broke
- A button only logs to console
- Data disappears after refresh
- Errors fail silently with no visible state
This is what should exist before you continue. If reality does not match, do not move on.
Track what changed, failed, or needs follow-up. Notes export with the flow.
Pass the Verify Gate to complete this step