oauth2-oidc

Probe OAuth2/OIDC flows for PKCE bypass and token handling misconfigurations.

846|152|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/xalgord/xalgorix --skill oauth2-oidc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oauth2-oidc
Source: https://github.com/xalgord/xalgorix/tree/main/internal/tools/skills/data/protocols/oauth2-oidc
Command: npx skills add https://github.com/xalgord/xalgorix --skill oauth2-oidc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps security teams validate OAuth 2.0 and OpenID Connect implementations by uncovering PKCE bypasses, token exchange abuse, and cross-client attack vectors.

Core Features & Use Cases

  • Flow-specific attacks across Authorization Code, PKCE, Device Authorization, and Token Introspection to identify misconfigurations and weaknesses.
  • Real-world attack scenarios including code reuse, downgrade, and cross-client token usage to validate defenses.
  • Use Case: Evaluate a production-like environment by running automated probe sequences against an OAuth/OIDC server and report findings.

Quick Start

Execute the oauth2-oidc skill against your OAuth2/OIDC provider to discover PKCE weaknesses and token handling vulnerabilities.

Frequently Asked Questions about oauth2-oidc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test OAuth2 and OIDC flows for PKCE bypass vulnerabilities?

To test OAuth2 and OIDC flows for PKCE bypass vulnerabilities, execute automated probe sequences against your authorization server to identify code exchange weaknesses, downgrade attacks, and token handling misconfigurations.

How does cross-client token abuse work in OpenID Connect implementations?

Cross-client token abuse in OpenID Connect occurs when tokens are improperly validated across clients. This Skill evaluates authorization servers to uncover token exchange abuse and cross-client attack vectors using standardized vulnerability checks.

Can I assess the device authorization flow and token introspection security of my provider?

Yes, you can assess device authorization flow and token introspection security by running defined probe sequences against your OAuth 2.0 provider to validate defenses and detect misconfigurations in a production-like environment.

What is the best way to automate vulnerability assessment for an OAuth 2.0 authorization server?

The best way to automate vulnerability assessment for an OAuth 2.0 authorization server is to execute standardized probe sequences covering authorization code, PKCE, and device flows to safely evaluate and report findings.

Are there limitations when testing OAuth2 token reuse and downgrade attacks?

Limitations when testing OAuth2 token reuse and downgrade attacks include relying on safe evaluation using defined probe sequences, meaning tests must target production-like environments rather than live systems to avoid disrupting active client sessions.