Skip to content

zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-runtime-routing

competition-runtime-routing

Verified

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.

FileKindSize
SKILL.mdskill md3.3 KB
agents/openai.yamlconfig376 B
references/runtime-routing.mdmarkdown984 B

references/runtime-routing.md

View on GitHub
# Runtime Routing Checklist

## Inputs That Commonly Matter

- `Host`, `X-Forwarded-Host`, `X-Forwarded-Proto`, `X-Forwarded-Port`
- Path prefixes, base path rewrites, tenant prefixes, cookie domain or path scope
- `Origin`, websocket upgrade headers, absolute URL generation, callback base URLs

## Route Map To Build

1. Client-visible host, scheme, port, and path
2. Reverse proxy or ingress rule that matches it
3. Target service, container, pod, or local process
4. Downstream store, worker, or peer node if the request fans out

## Verification Pattern

- Change one routing input at a time
- Compare both request traces and backend behavior
- Keep checked-in config separate from live config when they differ

## Common Pitfalls

- Treating a cloud-looking or public-looking hostname as external without checking sandbox routing
- Mixing auth failures with route resolution failures
- Explaining the path from code only without capturing one real request that proves the route
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall