id-token-reviewer

Validate OpenID Connect ID Tokens against OIDC Core specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ID Token validation tasks are error-prone and require strict adherence to the OpenID Connect Core specifications. This guide provides a structured review process to verify token structure, critical claims, and signature integrity.

Core Features & Use Cases

  • Checklist-driven review of ID Token fields (iss, sub, aud, exp, iat) and conditional claims (nonce, auth_time, azp, at_hash).
  • Validate signature with RS256 and verify using the provider's public keys.
  • Generate and report coverage gaps for test scenarios in Basic OP (Authorization Code Flow).

Quick Start

Review a sample ID Token against the checklist and produce a compliance report.

Frequently Asked Questions about id-token-reviewer

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

FAQPage Schema
How do I validate an OIDC ID Token against the OpenID Connect Core specifications?

To validate an OIDC ID Token, you must verify its structure, critical claims like iss and aud, and RS256 signature integrity using the provider's public keys. This process ensures compliance with OpenID Connect Core sections 3.1.3.6 and 3.1.3.7.

What claims are required when validating ID Tokens in the Authorization Code flow?

Required ID Token claims for validation include issuer, audience, expiration, and iat. Conditional claims such as nonce, auth_time, azp, and at_hash are also reviewed to ensure strict adherence to OpenID Connect profile specifications.

Does ID Token validation support signature algorithms other than RS256?

This validation process specifically supports RS256-based ID Tokens used within Basic OP. It verifies signatures by retrieving and applying the OpenID Connect provider's public keys to the token.

How do I verify the nonce claim in an OpenID Connect ID Token?

Verifying the nonce claim involves checking it against the value sent in the authentication request during the Authorization Code flow. This checklist-driven review confirms conditional claims like nonce meet OIDC expectations.

What is the best way to check ID Token compliance for test scenarios in Basic OP?

The best way to check ID Token compliance is using a structured checklist to review fields and generate a coverage gap report. This produces a compliance report verifying structure, claims, and signatures for Basic OP test scenarios.