dast-devils-advocate — Claude Code subagent: features and setup
dast-devils-advocate — an adversarial subagent that questions DAST findings, reruns PoC commands, flags publicly accessible data, and lowers inflated severity ratings before you submit reports.
no license ★ 1,298 updated 2026-06-12
.claude/agents/dast-devils-advocate.mdWhat dast-devils-advocate does
Automated bug hunting tools often exaggerate vulnerability impact. A 200 response code gets labeled as high-severity IDOR, while a reflected string is declared a critical injection. This agent challenges every claim. It replays the original curl commands, queries endpoints without credentials to confirm data is truly private, and consults policy.md and hacktivity.md for program exclusions.
Operating with Bash, Grep, Read, and WebFetch, the agent runs for up to 150 turns. Two modes exist: subtype: finding audits a single vulnerability, while subtype: exhaustion scrutinizes claims that an automated scan finished. Without browser confirmation, client-side scripts get blocked immediately. The subagent then outputs structured JSON with an adjusted title and recalibrated severity.
What it helps with
- Disprove inflated vulnerability claims prior to reporting
- Replay proof-of-concept curl requests to verify reproducibility
- Identify leaked data that is already publicly accessible
- Recalibrate bug severity based on observed technical impact
Example prompts for the agent
- Audit the finding in
findings/idor-01.jsonusingsubtype: findingbefore generating the final report. - Run
dast-devils-advocatewithsubtype: exhaustionto evaluate whether the automated scan thoroughly finished. - Review
findings/reflected-xss.jsonand downgrade severity if HttpOnly blocks cookie exfiltration.
How to install dast-devils-advocate
Manually: put the files in place
.claude/agents/dast-devils-advocate.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/dast-devils-advocate.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/dast-devils-advocate.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about dast-devils-advocate
How do I install dast-devils-advocate in Claude Code?
Place the agent configuration file at .claude/agents/dast-devils-advocate.md inside your repository.
What does dast-devils-advocate do?
The subagent tests incoming DAST findings adversarially by re-running PoC curls, verifying actual data exposure, and downgrading or rejecting unproven vulnerability claims.
How does the agent handle unverified client-side issues like XSS?
It marks them with a BLOCK verdict until proof is produced from an actual browser, preventing theoretical reflections from being reported as functional exploits.