Skip to content
SkillModel-led558 tokens in use

competition-oauth-oidc-chain

A CTF sandbox workflow for tracing OAuth and OIDC redirects, tokens and claims until the app accepts an identity.

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

121tokens idle
558tokens in use
784tokens, 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
  • Output12/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 guides an agent through an OAuth or OIDC flow in a CTF sandbox challenge: the entry route, authorize redirect, callback, token exchange, refresh and the service that finally accepts the identity.

It is meant for challenges where the hard part is showing how a flow is shaped and accepted. The agent records scopes, state, nonce, PKCE material, redirect URIs and token claims, then reduces the result to the smallest redirect-to-acceptance sequence. The skill replies in Simplified Chinese unless English is requested.

What You Get

  • A step order for mapping entry route, authorize request, callback, token exchange and refresh
  • A checklist of redirect-side, token-side and acceptance-side evidence to keep together
  • A rule that separates token possession from the point where a service accepts the identity
  • A pointer to the JWT claim confusion skill when the problem shifts to token validation

Common Use Cases

  • Explaining how a CTF login flow turns a callback code into an accepted session
  • Documenting scopes, audience, subject and expiry of tokens seen in a challenge
  • Reducing a long redirect trail to one canonical flow plus one minimal variant

What Makes It Unique

It is narrow: it covers only the OAuth and OIDC chain and hands off to sibling skills for JWT validation or general web routing. It insists on proving backend acceptance, not only browser-visible redirects, and it only runs 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. It does not tell the agent to fetch pages, call APIs or write files itself, though the agent’s own tools may be used to observe the challenge flow. It requires the orchestrator skill to be active first.

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