competition-template-render-path

competition-template-render-path is a skill for Codex from zhaoxuya520/reverse-skill. It costs 111 tokens per session (657 once invoked), scanned A, original, MIT.

A specialized guide for tracing how a server-rendered page is selected, populated, sent as HTML, and taken over by browser code. It is used within a larger capture-the-flag sandbox workflow.

In plain words
What is it for?
Use it to inspect server-side rendering routes, template data, hydration payloads, route parameters, and differences between template checks and handler enforcement.
Why use it?
It helps find gaps where a page appears protected but its data loader or server handler is not, or where server and browser rendering disagree.

Skill for Codex

Written for Codex: agents/openai.yaml present. Also seen: $skill-name invocation.

Good fit Use it to inspect server-side rendering routes, template data, hydration payloads, route parameters, and differences between template checks and handler enforcement.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zhaoxuya520/reverse-skill/competition-template-render-path
About the project

Reverse Skill is a routing package for AI coding agents that selects appropriate reverse-engineering, penetration-testing, and security-research methods and tools for a given target. It is used for tasks involving APKs, binaries, frontend JavaScript, packet captures, CTF challenges, and authorized penetration testing. Its catalogue add-ons provide the skills and instructions that guide these workflows.

zhaoxuya520/reverse-skill · 35,027 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add zhaoxuya520/reverse-skill --skill competition-template-render-path
Clone the repo
git clone --depth 1 https://github.com/zhaoxuya520/reverse-skill

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for competition-template-render-path

README.md
[![agentmods](https://agentmods.dev/badge/skills/zhaoxuya520/reverse-skill/competition-template-render-path.svg)](https://agentmods.dev/skills/zhaoxuya520/reverse-skill/competition-template-render-path)
Your own site
<a href="https://agentmods.dev/skills/zhaoxuya520/reverse-skill/competition-template-render-path"><img src="https://agentmods.dev/badge/skills/zhaoxuya520/reverse-skill/competition-template-render-path.svg" alt="Measured on agentmods" height="20"></a>
Per session 111 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 657 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00111 $0.00657
Opus 5 $0.00056 $0.00329
Sonnet 5 $0.00022 $0.00131
Haiku 4.5 $0.00011 $0.00066

Measured 8d ago against content hash 0bf311c5e7e5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

competition-template-render-path scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

CTF-Sandbox-Orchestrator/competition-template-render-path/SKILL.md · 51 lines

How it starts

The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Competition Template Render Path

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 bug or artifact lives in route resolution, server render context, template data, or hydration handoff rather than in a plain JSON API alone.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the render chain in order: route resolution, loader or data fetch, template or component context, response HTML, hydration payload, and client takeover.
  2. Record host, route params, preview toggles, tenant or host switches, and server-only variables before mutating anything.
  3. Compare template gating with loader or handler enforcement.
  4. Preserve one successful render and one failing render path with the smallest delta.
  5. Reproduce the smallest request-to-render branch that proves the decisive behavior.

Workflow

1. Map Route To Render Context

  • Record host, path, route match, loader, template, layout, hydration blob, and client boot chunk for the active view.
  • Note whether the response is SSR HTML, static HTML plus hydration, edge-rendered content, or a template fragment used by another route.
  • Keep server-only context and client-visible context separate.

2. Trace Template And Enforcement Boundaries

  • Show where permissions, feature flags, preview state, tenant selection, or host-based switches are applied.
  • Compare template-level gating, loader-level gating, and backend handler enforcement instead of trusting any one layer.
  • Record hidden fields, inline data, hydration JSON, meta tags, or alternate partials that expose the decisive branch.

3. Reduce To The Decisive Render Path

  • Compress the result to the smallest sequence: request -> route match -> loader or template context -> rendered output or hidden data -> resulting effect.
  • State clearly whether the decisive weakness lives in route selection, template context construction, server-client hydration handoff, or mismatched enforcement between render and handler.
  • If the task becomes mostly emitted bundle recovery or source map reconstruction, hand off to the tighter bundle skill.

Read the full file on GitHub · 51 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 51 lines · 111 tokens per session scan A 0bf311c5e7e5

Subscribe to this mod's changes

competition-template-render-path is a skill published in the GitHub repository zhaoxuya520/reverse-skill (35,027 stars, last pushed 5d ago), licensed MIT. It adds 111 tokens to every session and 657 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens