What problem does it solve? In CTF sandbox challenges, it is often unclear which host, container, or proxy rule actually serves a given route, especially when public-looking domains, forwarded headers, and path rewrites obscure the real request path. This Skill provides a structured workflow to map and prove route resolution end-to-end. ## Core Features & Use Cases - Route Mapping: Build a host -> proxy rule -> container -> process -> downstream store map for any live request. - Header Analysis: Systematically test Host, X-Forwarded-*, Origin, websocket upgrade, and path-prefix inputs to find the decisive routing branch. - Deviation Proof: Isolate the smallest request shape that flips tenant selection, cookie scope, or upstream target, separating routing decisions from application auth logic. - Use Case: During a CTF, a challenge presents a cloud-looking hostname and you need to know whether it belongs to the sandbox and which container serves it. This Skill walks you through tracing the route and proving it with one real request. ## Quick Start Ask the agent to map which sandbox node and proxy rule serves a given challenge route and prove it by replaying the request with one header changed at a time.
