Skip to content
SkillModel-led909 tokens in use

Competition Web Runtime

A CTF sandbox skill for web, API and worker-backed challenges: map the live runtime, capture real request order, and route to a narrower skill when needed.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-web-runtime
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 Web Runtime costs

110tokens idle
909tokens in use
1,142tokens, 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
  • Examples0/15
  • Output15/15
  • Size15/15
  • Resources5/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

Competition Web Runtime is a downstream skill of ctf-sandbox-orchestrator for challenges about web behavior, browser state, server routing, API order or worker-backed flows. It treats the sandbox hosts and routes as the lab and works from the real traffic.

The skill starts from entry HTML, boot scripts and runtime config, captures one request flow end to end, and only then widens to middleware, uploads, exports and background jobs. It also lists which narrower skill to use for SSR, bundles, GraphQL, SSRF, races, OAuth, JWT, queues, WebSockets and routing. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A three-stage workflow: map the active runtime, capture the real request order, expand only after one path is proven
  • A routing table to a dozen narrower competition skills, from SSR and bundle recovery to OAuth, JWT, queues and WebSockets
  • A checklist of high-value web targets such as hidden routes, auth minting, upload and export boundaries, and worker side effects
  • A reference note on one cookie-signing weakness found in a lab target, kept as a worked case

Common Use Cases

  • Following a browser session through a CTF web challenge and explaining why frontend and backend behavior differ
  • Inspecting browser persistence together with backend state while debugging an auth or session flow
  • Tracing uploads, exports and background workers in a lab application
  • Choosing which narrower skill to load once the dominant theme of a challenge is clear

What Makes It Unique

It works as a hub. Where other web skills pick one vulnerability class, this one sets the evidence discipline (one proven flow first, one variable changed at a time) and points to the specialised skills in the same package when the challenge matches one. The bundled reference documents a signing-key reuse case from a lab target as a worked example.

Under The Hood

The skill is a markdown workflow with two reference files and an agent metadata file. It ships no scripts. The instructions direct the agent to inspect the sandbox target, so the agent will fetch pages, send requests, read browser storage and may run shell commands through the client. The cookie case reference contains example code and command lines for a lab target; this page does not reproduce them. The skill states that it applies only after the orchestrator has set sandbox assumptions.

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