competition-runtime-routing

Trace hostname, proxy rule, or path prefix resolution to live sandbox services.

4|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-runtime-routing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-runtime-routing
Source: https://github.com/xjtu-wang/DigAgent/tree/main/.agents/skills/competition-runtime-routing
Command: npx skills add https://github.com/xjtu-wang/DigAgent --skill competition-runtime-routing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for reverse proxies, Host headers, forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting, base-URL derivation, and multi-node route resolution. Use when the user asks which host or container serves a route, why a public-looking domain still belongs to the sandbox, how headers or proxies change behavior, or how a route resolves across proxy, container, and worker boundaries. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.

Core Features & Use Cases

  • Routing map construction: map host, proxy rule, target service, and downstream process for a live route.
  • Header provenance tracking: record Host, X-Forwarded-Host, X-Forwarded-Proto, and related headers used in routing decisions.
  • Audit-ready evidence generation: preserve maps and traces for verification across sandbox boundaries.

Quick Start

Assume the sandbox is active and map a live route from host to proxy rule to service, documenting each step and the involved headers.

Frequently Asked Questions about competition-runtime-routing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I trace proxy routing across sandboxed containers and services?

Trace proxy routing across sandboxed containers by mapping hostnames, proxy rules, and path prefixes to concrete live services, recording the exact route map and involved headers as evidence for verification.

How do Host headers and forwarded headers affect route resolution in a sandbox?

Host headers and forwarded headers like X-Forwarded-Host and X-Forwarded-Proto drive vhost routing decisions, mapping public-looking domains to internal sandbox containers and downstream processes during route resolution.

Why does a public-looking domain still route to an internal sandbox container?

A public-looking domain routes to an internal sandbox container because proxy rules, path-prefix rewriting, and base-URL derivation bind the host header to a specific live service inside the sandbox environment.

How do websocket upgrades influence routing decisions across proxy and container boundaries?

Websocket upgrades influence routing decisions across proxy and container boundaries by requiring specific proxy rules and header handling to maintain the connection to the correct downstream worker or target service.

Can I use this route resolution approach for multi-node deployment debugging?

Yes, you can use this route resolution approach for multi-node deployment debugging. It traces how a path prefix or proxy rule resolves across proxy, container, and worker boundaries to identify the live target service.

What prerequisites are needed before tracing sandbox route resolution?

Tracing sandbox route resolution requires an active sandbox environment with established sandbox assumptions already routed, ensuring the proxy rules, hostnames, and base URLs are live and available for mapping.