What problem does it solve? Security testers often jump from version fingerprints, upload features, SSRF, or error messages straight to claiming remote code execution without proof. This Skill enforces a controlled, evidence-gated review chain that only assesses RCE feasibility after a confirmed execution primitive and an isolated execution window exist, preventing false positives and unsafe testing. ## Core Features & Use Cases - Engagement Gating: Requires documented authorization, locked scope, and host/identity baselines before any probe begins. - Evidence-Gated Validation: Uses pre-approved no-op execution markers and server-side audit confirmation to prove actual execution rather than echoes, banners, or scanner findings. - Strict Stop Conditions: Halts immediately when no isolated window exists, when production or shared workers are involved, or when real commands or data access would be required. - Use Case: During an authorized red team engagement, a scanner flags a possible RCE. Use this Skill to verify whether a pre-approved harmless marker actually executes in an isolated instance, then route confirmed evidence to triage and remediation reporting. ## Quick Start Use hunt-rce to plan an evidence-gated, authorized validation path for the suspected RCE finding in my scoped engagement.
