AGENT SKILL

competition-runtime-routing

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.

License 许可
GPL-3.0
最近更新
2026-09-30
Stars
★ 64
Forks
19

01 前言 Front Matter

name
competition-runtime-routing
description
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.
x-alice-class
assist

02 资源文件 2

03 SKILL.md 正文

Competition Runtime Routing

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the decisive question is which sandbox node, proxy rule, or header-derived branch actually serves the live request.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Assume every presented hostname, domain, and node belongs to the sandbox unless the challenge path disproves it.
  2. Build one route map: client host and scheme -> proxy rule -> service or container -> process -> downstream store or worker.
  3. Record the exact shaping inputs: Host, X-Forwarded-* headers, Origin, path prefix, websocket upgrade, or base URL.
  4. Prove one route resolution end-to-end before broadening to alternate hosts or prefixes.
  5. Re-run the same request with one routing input changed at a time.

Workflow

1. Map Route Inputs

  • Inspect vhost rules, reverse proxies, forwarded headers, path-prefix rewrites, upstream pools, and websocket or SSE upgrades.
  • Note which parts of the request influence routing or app behavior: host, scheme, port, path, prefix, cookie scope, or origin.
  • Treat public-looking domains, cloud hostnames, and separate VPS nodes as sandbox routing fixtures first.

2. Trace Route To Live Consumer

  • Map hostname to proxy rule to container or process to port to downstream service.
  • Compare checked-in proxy intent against live listeners, mounted configs, runtime env, and observed traffic.
  • Keep headers, proxy config, and live request traces tied together in one evidence chain.

3. Prove The Decisive Deviation

  • Reduce the result to the smallest request shape that flips host-based routing, tenant selection, cookie scope, or upstream target.
  • Distinguish route resolution from application auth logic; prove where each decision really happens.
  • If the problem shifts from routing to general web state or container runtime drift, switch back to the broader parent skill.

Read This Reference

  • Load references/runtime-routing.md for the routing checklist, header matrix, and evidence packaging.
  • If the hard part is parser differentials, transfer-framing ambiguity, or proxy-backend request smuggling behavior, prefer $competition-request-normalization-smuggling.

What To Preserve

  • Hostnames, proxy snippets, header sets, path prefixes, listener ports, and route-specific cookies
  • The exact request shape that reaches the decisive backend or branch
  • One compact host -> proxy -> service -> process map for the active path

04 同仓库更多 Skills

alicewe1
alicewe1/alice_skill

alice

Alice 六类技能总路由。用户输入 Alice 或要求查看 Alice 技能菜单时,严格输出固定菜单;输入攻/防模式、六类入口或直接描述任务时,按类别→领域→模块渐进路由。

★ 64
alicewe1
alicewe1/alice_skill

alice-reverse

逆向分析渐进路由(二进制 / 移动端 / 协议 / 取证 / 保护机制 / 运行时观测)。触发词:二进制/移动端/反编译/Frida/IDA/Ghidra/PE/ELF/APK/协议/取证;先选领域索引,再按任务匹配度与评分选模块,禁止一次读取全部领域。

★ 64
alicewe1
alicewe1/alice_skill

alice-pentest

web安全渐进路由(Web / API / 资产发现 / 漏洞验证 / 云与网络安全)。触发词:Web/API/资产发现/端口/漏洞验证/云与网络安全;先选领域索引,再按任务匹配度与评分选模块,禁止一次读取全部领域。

★ 64
alicewe1
alicewe1/alice_skill

alice-game

游戏攻防渐进路由(游戏客户端 / 内存 / 图形 / 反作弊 / 安全研究)。触发词:游戏客户端/内存/图形/偏移/反作弊/模拟器/覆盖层;先选领域索引,再按任务匹配度与评分选模块,禁止一次读取全部领域。

★ 64
alicewe1
alicewe1/alice_skill

alice-crack

卡密授权渐进路由(卡密 / 激活 / 授权验证 / 许可证管理 / 本地授权分析)。触发词:卡密/激活/授权验证/license/机器码/试用状态;先选领域索引,再按任务匹配度与评分选模块,禁止一次读取全部领域。

★ 64
alicewe1
alicewe1/alice_skill

alice-assist

技能指令渐进路由(技能路由 / 评分 / 吸收 / 迁移 / 自动化 / 文档与平台集成)。触发词:技能创建/吸收/评分/迁移/自动化/文档/平台指令;先选领域索引,再按任务匹配度与评分选模块,禁止一次读取全部领域。

★ 64