Skip to content
SkillModel-led558 tokens in use

competition-runtime-routing

A CTF sandbox workflow for working out which host, proxy rule or container serves a route and how headers change it.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-runtime-routing
git clone https://github.com/zhaoxuya520/reverse-skill.git
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing competition-runtime-routing costs

121tokens idle
558tokens in use
776tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a downstream specialization of the ctf-sandbox-orchestrator skill. It covers reverse proxies, Host and forwarded headers, vhost routing, websocket upgrades, path-prefix rewriting and multi-node route resolution in a CTF sandbox.

The agent builds one route map from client host to proxy rule, service, process and downstream store, then changes one routing input at a time to find the smallest request shape that flips the route. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A route map template: client host, proxy rule, service or container, process and downstream store
  • A list of routing inputs: Host, X-Forwarded headers, Origin, path prefix, upgrade headers and base URLs
  • A one-input-at-a-time verification pattern
  • A hand-off pointer to the request smuggling skill for parser differentials

Common Use Cases

  • Finding which container answers a public-looking hostname in a lab
  • Explaining how a forwarded header changes tenant or cookie scope in a sandbox app
  • Comparing checked-in proxy config with live listeners in a CTF environment

What Makes It Unique

It starts from the assumption that presented hostnames and cloud-looking domains are sandbox fixtures, and it separates route resolution from application auth logic. It leaves parser-differential cases to a sibling skill and runs only after the orchestrator skill has set sandbox assumptions.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent config file that disables implicit invocation. It ships no scripts and does not itself fetch pages, call APIs, run commands or write files. The agent uses tools the user already provides to send requests and inspect proxy config in the sandbox.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers