Rank attack surface for: $ARGUMENTS
- Verify recon data exists in recon/ directory. If not, suggest /recon first.
- Read brain data for this target.
- Launch
recon-ranker agent: "Rank the attack surface for $ARGUMENTS. Read recon/ for discovery data and brain for tested endpoints. Output P1/P2/Kill ranking."
- Show the ranking to the user.
- Suggest:
/hunt $ARGUMENTS to start testing P1 targets.
Top-Tier Surface Ranking
Rank by exploit economics.
P1 requires at least two of:
- crown-jewel function: auth, billing, admin, tenant data, integrations, uploads, exports, webhooks, AI/tool execution
- weak boundary: cross-tenant IDs, mixed roles, public/private transition, OAuth callback, parser boundary, file ingestion
- novelty: new asset, changed JS, low hacktivity coverage, unusual vendor or beta endpoint
- proof path: two-account test, clear callback, readable response, browser-verifiable sink, local PoC
Kill or P3 assets that are static marketing pages, hardened vendor panels with no program-owned data, or endpoints already exhausted with strong evidence. Every P1 must include the best first vuln class and first request to try.
1---2name: surface-23description: "Show ranked attack surface for a target. Invokes recon-ranker agent. Usage: /surface target.com"4---56Rank attack surface for: $ARGUMENTS781. Verify recon data exists in recon/ directory. If not, suggest /recon first.92. Read brain data for this target.103. Launch `recon-ranker` agent: "Rank the attack surface for $ARGUMENTS. Read recon/ for discovery data and brain for tested endpoints. Output P1/P2/Kill ranking."114. Show the ranking to the user.125. Suggest: `/hunt $ARGUMENTS` to start testing P1 targets.1314## Top-Tier Surface Ranking1516Rank by exploit economics.1718P1 requires at least two of:19- crown-jewel function: auth, billing, admin, tenant data, integrations, uploads, exports, webhooks, AI/tool execution20- weak boundary: cross-tenant IDs, mixed roles, public/private transition, OAuth callback, parser boundary, file ingestion21- novelty: new asset, changed JS, low hacktivity coverage, unusual vendor or beta endpoint22- proof path: two-account test, clear callback, readable response, browser-verifiable sink, local PoC2324Kill or P3 assets that are static marketing pages, hardened vendor panels with no program-owned data, or endpoints already exhausted with strong evidence. Every P1 must include the best first vuln class and first request to try.