Skip to content
SkillModel-led444 tokens in use

competition-request-normalization-smuggling

A CTF sandbox workflow for studying HTTP parser differences between proxy and backend layers, using paired baseline requests.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-request-normalization-smuggling
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-request-normalization-smuggling costs

110tokens idle
444tokens in use
638tokens, 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
  • Output10/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 challenges where request interpretation changes between a proxy, middleware and a backend parser: path normalization, header canonicalization, Host derivation and transfer framing.

The agent maps every parsing hop, builds paired requests that differ in one dimension, captures proxy and backend evidence and reduces the result to one minimal differential path. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A hop-by-hop map of proxy, gateway, app server and downstream parsing
  • A paired-request method that changes one canonicalization dimension at a time
  • Guidance to compare proxy logs, backend logs and route matches
  • A root-cause statement format: path drift, header ambiguity, framing differential or host derivation

Common Use Cases

  • Explaining why a proxy and a backend route the same path differently in a lab
  • Documenting Host or forwarded-header ambiguity in a sandbox CTF
  • Recording a length or chunk framing mismatch between two hops

What Makes It Unique

It insists on one changed field per request pair so the cause stays attributable, and it asks for backend route evidence as well as front proxy logs. It hands off to the runtime routing skill when no framing issue is involved, and it 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 or payloads and does not itself fetch pages, call APIs, run commands or write files. Any requests are sent with tools the user provides, against sandbox targets they are authorized to test.

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