web-security-posture-wasp-drone — Claude Code subagent
web-security-posture-wasp-drone is a Claude Code subagent for passive security checks on external websites. It examines headers, cookies, CSP, and observable client-side risks.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install website-audit-tools@wasp-nestWhat web-security-posture-wasp-drone does
The subagent assesses a third-party site's public security posture through HTTP responses, headers, and cookies. It reviews CSP, makes a coarse TLS reachability check, and compares client-side exposure with the vendor inventory. Payment-path checks stay observational.
It needs site-data/ and 01-recon/vendor-inventory.md as inputs. The subagent runs shared/scripts/security-headers.py, writes findings to 07-security/, and updates _shared/evidence-index.md.
It does not log in, exploit the site, or send requests that change its state. It does not assess certificate-chain depth or TLS cipher strength; payment-path integrity is checked only within the supported observational scope. Security carries 20% of the final score.
What it helps with
- inspect HTTP headers and cookie flags on an external site
- review CSP and perform a coarse TLS check
- compare client-side exposure with the vendor inventory
- record observable payment-path risks
Example prompts for the agent
- Run a passive security check using the material in
site-data/. - Compare client-side scripts with
01-recon/vendor-inventory.mdand save findings under07-security/. - Review the site's headers and CSP for the pages listed in
site-data/.
How to install web-security-posture-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install website-audit-tools@wasp-nest2Manually: put the files in place
.claude/agents/web-security-posture-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/web-security-posture-wasp-drone.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/web-security-posture-wasp-drone.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 web-security-posture-wasp-drone
How do I install web-security-posture-wasp-drone in Claude Code?
Run these in order: /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install website-audit-tools@wasp-nest, then .claude/agents/web-security-posture-wasp-drone.md.
What does web-security-posture-wasp-drone do?
It passively checks a third-party site's public security posture, including HTTP headers, cookies, CSP, TLS reachability, and client-side exposure. Findings go to 07-security/.
What does web-security-posture-wasp-drone need to run?
It needs site-data/ and 01-recon/vendor-inventory.md. It runs shared/scripts/security-headers.py and avoids checks that change the site's state.