What is configuring-oauth2-authorization-flow?

A guide to configuring OAuth 2.0, a standard that lets an application obtain limited access to a user’s or service’s resources without handling the user’s password. It covers browser sign-in, machine-to-machine access, device sign-in, scopes, and token management.

Use it to choose and implement Authorization Code with PKCE, Client Credentials, or Device Authorization flows for applications and APIs.

It helps applications grant narrowly defined access and manage access tokens safely, including their renewal and revocation.

configuring-oauth2-authorization-flow — Skill by andycungkrinx91

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add andycungkrinx91/konoha --skill configuring-oauth2-authorization-flow

Clone the repo

git clone --depth 1 https://github.com/andycungkrinx91/konoha

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/andycungkrinx91/konoha/configuring-oauth2-authorization-flow/github.svg)](https://agentmods.dev/skills/andycungkrinx91/konoha/configuring-oauth2-authorization-flow)

Your own site

<a href="https://agentmods.dev/skills/andycungkrinx91/konoha/configuring-oauth2-authorization-flow"><img src="https://agentmods.dev/badge/skills/andycungkrinx91/konoha/configuring-oauth2-authorization-flow/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/andycungkrinx91/konoha/configuring-oauth2-authorization-flow"><img src="https://agentmods.dev/badge/skills/andycungkrinx91/konoha/configuring-oauth2-authorization-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,523 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 92% copy Near-identical to another mod in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.01523
Opus 5.5	$0.00018	$0.00609
Sonnet 5.5	$0.00009	$0.00305
Haiku 4.5	$0.00004	$0.00152

Measured today against content hash 64a38041003b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

configuring-oauth2-authorization-flow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/agent.py, scripts/process.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

Origin

This is a copy

92% identical to configuring-oauth2-authorization-flow — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/akatsuki-skill/references/anthropic-cybersecurity-skills-assets/skills/configuring-oauth2-authorization-flow/SKILL.md · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configuring OAuth 2.0 Authorization Flow

Overview

Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token lifecycle management, scope design, and alignment with OAuth 2.1 security requirements.

When to Use

When deploying or configuring configuring oauth2 authorization flow capabilities in your environment
When establishing security controls aligned to compliance requirements
When building or improving security architecture for this domain
When conducting security assessments that require this implementation

Prerequisites

Familiarity with identity access management concepts and tools
Access to a test or lab environment for safe execution
Python 3.8+ with required dependencies installed
Appropriate authorization for any testing activities

Objectives

Implement Authorization Code flow with PKCE for public and confidential clients
Configure Client Credentials flow for machine-to-machine communication
Design least-privilege scope hierarchies
Implement secure token storage, refresh, and revocation
Apply OAuth 2.1 best practices and RFC 9700 security recommendations
Validate token integrity and prevent common OAuth attacks

Key Concepts

OAuth 2.0 Grant Types

Authorization Code + PKCE: Recommended for all client types (web, mobile, SPA). PKCE is mandatory in OAuth 2.1.
Client Credentials: Machine-to-machine authentication without user context.
Device Authorization Grant (RFC 8628): For input-constrained devices (smart TVs, CLI tools).
Refresh Token: Long-lived token to obtain new access tokens without re-authentication.

PKCE (Proof Key for Code Exchange)

PKCE (RFC 7636) prevents authorization code interception attacks:

Client generates random code_verifier (43-128 characters, unreserved URI chars)
Client computes code_challenge = BASE64URL(SHA256(code_verifier))
Authorization request includes code_challenge and code_challenge_method=S256
Token request includes original code_verifier
Server validates SHA256(code_verifier) matches stored code_challenge

Read the full file on GitHub · 170 lines

Files

What ships with it

6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 170 lines · 44 tokens per session scan A 64a38041003b

Subscribe to this mod's changes

configuring-oauth2-authorization-flow is a skill published in the GitHub repository andycungkrinx91/konoha (12 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,523 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 92% identical to configuring-oauth2-authorization-flow, differing in 22 lines, and is treated as a copy.

Backend and APIs Security access-control authentication authorization iam identity oauth2 oidc pkce