Skip to content
SkillModel-led543 tokens in use

Competition Template Render Path

A CTF sandbox skill that follows a request through route match, loader, template context and hydration data to find where render and handler checks diverge.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-template-render-path
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 Template Render Path costs

112tokens idle
543tokens in use
773tokens, 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
  • Output15/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

Competition Template Render Path is a downstream skill of ctf-sandbox-orchestrator for challenges where the decisive behavior lives in server-side rendering, template data or hydration handoff. It guides an agent through the render chain from route resolution to client takeover.

It is meant for CTF and lab environments that the orchestrator has already set up. The skill compares template-level gating, loader-level gating and backend handler enforcement, and packages the smallest request-to-render sequence as evidence. Replies are in Simplified Chinese unless English is requested.

What You Get

  • A step-by-step workflow from route match to loader, template context, emitted HTML, hydration payload and client takeover
  • A checklist of what to record on the first pass: host, route params, preview toggles, hidden fields, meta tags and inline data
  • A way to compare template gating with loader and handler enforcement
  • An evidence layout that keeps route side, render side and effect side together, with one success and one failure pair

Common Use Cases

  • Explaining why a preview or hidden route renders content that the visible interface does not offer in a CTF lab
  • Finding hydration JSON or inline data blobs that expose a branch the template hides
  • Checking whether feature flags or tenant switches are enforced by the loader, the template or the backend handler
  • Writing up a render-layer finding with a minimal request-to-render sequence

What Makes It Unique

Most web skills treat the page as an HTTP response. This one treats the render pipeline as the object of study: route selection, context construction and hydration are separate stages, and a finding has to say which stage holds the weakness. It also hands off to the bundle and source map skill when the work turns into recovering emitted bundles, so the scope stays narrow.

Under The Hood

The skill is a markdown workflow with one reference checklist and an agent metadata file that disables implicit invocation, so it only runs after the orchestrator routes to it. It ships no scripts. The instructions tell the agent to inspect requests and responses of the sandbox target, so the agent will issue web requests and run whatever commands the session allows. It writes nothing on its own beyond the evidence the user asks for.

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