Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-oauth-oidc-chainAPIs, SaaS and identity

competition-oauth-oidc-chain

⁨Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for OAuth, OIDC, redirect flows, state or nonce handling, PKCE, token exchange, refresh logic, claim mapping, and accepted login paths. Use when the user asks to trace redirects, callback parameters, scopes, state, nonce, P⁩

v2026.9.22-cab634b3 installs+3 in 7 days44.8K StarsMITsynced 2 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-oauth-oidc-chain

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
beh65I9Eyk…Y1OVZrAg==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb31e05eb…9fbb33ad
b31e05eb081e…2d4e9fbb33ad3 files · ⁦2.1 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-oauth-oidc-chain@cab634b

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 hard part is proving how an OAuth or OIDC flow is shaped, exchanged, and ultimately accepted.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Map the auth chain in order: entry route, redirect, authorize request, callback, token exchange, refresh, and final accepting service.
  2. Record scopes, state, nonce, PKCE material, redirect URIs, and claim-bearing tokens before mutating anything.
  3. Separate token possession from actual identity acceptance.
  4. Keep browser-visible redirects and backend-visible token exchange in one compact chain.
  5. Reproduce the smallest redirect-to-acceptance flow that proves the decisive identity edge.

Workflow

1. Map The Redirect And Token Path

  • Record issuer, client ID, redirect URI, authorize parameters, callback parameters, token endpoint, and refresh path.
  • Note which values are user-controlled, derived, cached, or validated: state, nonce, PKCE verifier, audience, scope, or prompt.
  • Keep browser redirects, server-side exchanges, and resulting session state tied together.

2. Prove Token-To-Identity Acceptance

  • Show how code, ID token, access token, or refresh token turns into app session, claims mapping, tenant selection, or accepted privilege.
  • Record token claims, expiration, audience, subject, scopes, and the exact accepting app or backend edge.
  • Distinguish UI login success from backend authorization success.

3. Reduce To The Decisive OAuth Chain

  • Compress the result to the smallest sequence: entry request -> redirect -> callback -> token or claim acceptance -> resulting capability.
  • Keep one canonical good flow and one minimal mutated flow if a parameter change matters.
  • If the task broadens into generic web routing or storage behavior outside the auth chain, switch back to the broader web-runtime skill.

Read This Reference

  • Load references/oauth-oidc-chain.md for the redirect checklist, token checklist, and evidence packaging.
  • If the hard part is JWT header parsing, claim normalization, key lookup, or token validation confusion after issuance, prefer $competition-jwt-claim-confusion.

What To Preserve

  • Redirect URIs, parameters, codes, token claims, scopes, and the accepting service or callback
  • The exact point where claims or tokens become accepted app identity
  • One minimal replayable redirect-to-acceptance sequence

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.9.22-cab634bNov 13, 2026cab634bb31e05ebSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login