← ClaudeAtlas

security-vuln-gauntletlisted

Apply the Gauntlet Loop to security vulnerability hunting — a hunter (builder) proposes candidate vulnerabilities and a blind validator (critic) inspects the real artifact and MUST build a working non-destructive PoC before anything is confirmed. The bar is exploitability + CWE mapping + real vulnerability-class precedent; false positives are killed by reachability → taint → PoC gates. Use ONLY on assets you own or are authorized in writing to test; every PoC must be non-destructive. Covers web, API, binary/memory, and cloud/IaC. Trigger keywords: "find vulnerabilities", "security code review", "pentest", "kill false positives", "IDOR", "BOLA", "SQL injection", "SSRF", "path traversal", "exploit PoC", "CWE", "OWASP Top 10", "triage this scan". Use together with the core gauntlet-loop skill.
trilwu/gauntlet-loop-skills · ★ 3 · AI & Automation · score 66
Install: claude install-skill trilwu/gauntlet-loop-skills
# Security Vuln Gauntlet The Gauntlet Loop applied to **finding real vulnerabilities**: a **HUNTER** (builder) proposes candidates and a blind **VALIDATOR** (critic) demands a **working PoC** before anything counts. The bar is **exploitability + CWE mapping + real precedent**. Covers **web, API, binary/memory, and cloud/IaC**. > Kept separate from the core `gauntlet-loop` skill because its **triggers and safety requirements differ**: written authorization (ROE) is mandatory and every PoC must be non-destructive. The method itself is the core loop. ## SCOPE AND AUTHORIZATION — mandatory Use only on assets you **own or are authorized in writing to test**. If there is no ROE, **STOP** and ask the user for one. Read `references/safety-and-scope.md` first. Every PoC must be **non-destructive**: no data destruction, no lateral movement, no exfiltration, no denial of service. This is a defensive/AppSec tool. Unauthorized access is a crime in most jurisdictions (CFAA in the US, the Computer Misuse Act in the UK, equivalent computer-crime statutes elsewhere) and the operator carries that responsibility. ## When to use it Reviewing or pentesting an authorized codebase, service, binary, or cloud configuration — or triaging an existing scan down to what is actually exploitable. ## Role mapping | Core role | Security role | |-----------|---------------| | LEAD | Split by trust boundary / entry point / high-value asset; maintain the coverage map | | BUILDER | **HUNTER** (clean con