token-endpoint-reviewer

Audit OAuth2/OIDC Token Endpoint test cases against specification requirements.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/maronnjapan/maronn-openid-provider --skill token-endpoint-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: token-endpoint-reviewer
Source: https://github.com/maronnjapan/maronn-openid-provider/tree/main/.claude/skills/token-endpoint-reviewer
Command: npx skills add https://github.com/maronnjapan/maronn-openid-provider --skill token-endpoint-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenID Connect and OAuth 2.1 implementations require rigorous validation of the Token Endpoint. This skill provides a structured review process to ensure test coverage across the authorization_code flow, client authentication methods, and token response validation.

Core Features & Use Cases

  • Checklist-driven evaluation of token endpoint requirements against OIDC Core 1.0 Section 3.1.3 and OAuth 2.1 references.
  • Verifies support for grant_type=authorization_code, client_secret_basic, and client_secret_post, including common error scenarios like invalid_client and invalid_grant.
  • Generates a concise conformance report and identifies gaps for QA and security audits.

Quick Start

Run the reviewer against your token endpoint test suite to generate a conformance report.

Frequently Asked Questions about token-endpoint-reviewer

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

FAQPage Schema
How do I validate my OAuth2 Token Endpoint against the OIDC Core specification?

Validate your OAuth2 Token Endpoint by auditing test cases against OIDC Core 1.0 Section 3.1.3 and OAuth 2.1 references. This process checks required parameters, token response fields, and code reuse protections to generate a conformance report identifying test coverage gaps.

What Token Endpoint error scenarios should I test for OAuth2 conformance?

Token Endpoint conformance testing should cover invalid_client and invalid_grant error scenarios. It also verifies proper handling of the authorization_code flow with client_secret_basic and client_secret_post authentication methods across various client configurations.

Does this token endpoint review process support grant types other than authorization_code?

Token endpoint review focuses exclusively on the authorization_code grant type. It does not process other grant types, instead ensuring deep compliance with required parameters and client authentication methods for this specific flow.

How do I check for authorization code reuse vulnerabilities in my OIDC implementation?

Check for authorization code reuse by mapping test cases to specific spec sections enforcing code reuse protections. The review process verifies that your token endpoint correctly invalidates codes after initial use to prevent replay attacks.

What is the best way to generate a conformance report for OAuth2 token response validation?

Generate a conformance report by running a checklist-driven evaluation of token endpoint requirements. This review audits token response fields and maps each compliance criterion to referenced OAuth 2.1 and OIDC spec sections, outputting a concise gap analysis.