Fortify Development
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration.
$ npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills oauth-2-0-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/api-and-integration/oauth-2-0-setup .claude/skills/oauth-2-0-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "oauth-2-0-setup" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setup into .claude/skills/oauth-2-0-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oauth-2-0-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills oauth-2-0-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/api-and-integration/oauth-2-0-setup .agents/skills/oauth-2-0-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "oauth-2-0-setup" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setup into .agents/skills/oauth-2-0-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oauth-2-0-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills oauth-2-0-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/api-and-integration/oauth-2-0-setup .cursor/skills/oauth-2-0-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "oauth-2-0-setup" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setup into .cursor/skills/oauth-2-0-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oauth-2-0-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/seb1n/awesome-ai-agent-skills.git --path api-and-integration/oauth-2-0-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills oauth-2-0-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/api-and-integration/oauth-2-0-setup .gemini/skills/oauth-2-0-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "oauth-2-0-setup" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setup into .gemini/skills/oauth-2-0-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oauth-2-0-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install seb1n/awesome-ai-agent-skills oauth-2-0-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/api-and-integration/oauth-2-0-setup .github/skills/oauth-2-0-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "oauth-2-0-setup" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setup into .github/skills/oauth-2-0-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oauth-2-0-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install seb1n/awesome-ai-agent-skills oauth-2-0-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/seb1n/awesome-ai-agent-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/api-and-integration/oauth-2-0-setup .opencode/skills/oauth-2-0-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "oauth-2-0-setup" agent skill from https://github.com/seb1n/awesome-ai-agent-skills/tree/main/api-and-integration/oauth-2-0-setup into .opencode/skills/oauth-2-0-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "oauth-2-0-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
oauth-2-0-setupImplement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration.
OAuth 2 0 Setup is an agent skill from seb1n/awesome-ai-agent-skills. Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.
Its SKILL.md is about 3.6k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering OAuth and OpenID Connect. The repository describes itself as: 103 ready-to-use AI agent skills for Claude Code, OpenAI Codex, Gemini CLI, Cursor, GitHub Copilot, Windsurf, and other Agent Skills-compatible tools. Complete SKILL.md… The licence is MIT.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 75865a5. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are javascript and python).
From the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
accounts.google.comoauth2.googleapis.comgoogleapis.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
SESSION_SECRETM2M_CLIENT_SECRETFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
OAuth 2 0 Setup loads about 3.6k tokens when it runs. Until then it costs about 63 tokens; SKILL.md has 949 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from seb1n/awesome-ai-agent-skills at commit 75865a5, republished under its MIT licence (© seb1n). 949 words, ~3,633 tokens.
.claude/skills/oauth-2-0-setup/SKILL.md (or your agent's skills folder).This skill enables an AI agent to implement OAuth 2.0 authentication for API integrations. The agent selects the appropriate grant type for the use case—authorization code with PKCE for user-facing apps, client credentials for machine-to-machine auth, and device code for input-limited devices. It handles token storage, refresh token rotation, CSRF protection via the state parameter, and secure credential management throughout the flow.
Select the appropriate grant type: Choose the OAuth 2.0 flow based on the client type. Use authorization code with PKCE for web and mobile apps where a user is present—PKCE replaces the client secret and prevents authorization code interception attacks. Use client credentials for server-to-server communication with no user context. Use device code flow for CLI tools or smart TVs where browser-based login isn't possible. Implicit flow is deprecated and should not be used.
Register the application with the provider: Create an OAuth application in the provider's developer console (Google, GitHub, Auth0, etc.). Configure the redirect URI precisely—mismatched URIs are the most common setup error. For PKCE flows, mark the application as a public client. Record the client ID, client secret (if applicable), authorization endpoint, token endpoint, and scopes.
Implement the authorization request: Construct the authorization URL with the required parameters: client_id, redirect_uri, response_type=code, scope, and a cryptographically random state parameter for CSRF protection. For PKCE, generate a random code_verifier (43-128 characters), derive the code_challenge using SHA-256, and include both code_challenge and code_challenge_method=S256 in the request. Store the state and code_verifier in the session.
Handle the callback and exchange tokens: When the provider redirects back with the authorization code, first verify the state parameter matches what was stored in the session. Then exchange the code for tokens by POSTing to the token endpoint with grant_type=authorization_code, the authorization code, redirect_uri, client_id, and the code_verifier (for PKCE). Parse the response for access_token, refresh_token, expires_in, and token_type.
Store tokens securely: Never store tokens in localStorage (XSS vulnerable) or URL parameters (logged in server access logs). Use HTTP-only secure cookies for web apps, the system keychain for desktop apps, and encrypted storage for mobile apps. Store refresh tokens server-side when possible. Record token expiration timestamps so you can proactively refresh before expiry.
Implement token refresh and rotation: Before each API call, check if the access token is expired or about to expire (within a 60-second window). If so, use the refresh token to get a new access token. Handle refresh token rotation—when the provider issues a new refresh token alongside the new access token, store the new refresh token and invalidate the old one. If refresh fails with an invalid_grant error, the user must re-authenticate.
Provide the agent with the OAuth provider, the type of application (web app, SPA, CLI, server-to-server), and the required scopes. The agent will select the correct grant type and produce a complete implementation including the authorization flow, token exchange, secure storage, and refresh logic.
const express = require("express");
const crypto = require("crypto");
const session = require("express-session");
const app = express();
app.use(session({
secret: process.env.SESSION_SECRET,
resave: false,
saveUninitialized: false,
cookie: { secure: true, httpOnly: true, sameSite: "lax", maxAge: 3600000 },
}));
const OAUTH_CONFIG = {
clientId: process.env.OAUTH_CLIENT_ID,
authorizationEndpoint: "https://accounts.google.com/o/oauth2/v2/auth",
tokenEndpoint: "https://oauth2.googleapis.com/token",
redirectUri: "https://myapp.com/auth/callback",
scopes: ["openid", "email", "profile"],
};
// Generate PKCE code verifier and challenge
function generatePKCE() {
const verifier = crypto.randomBytes(32).toString("base64url");
const challenge = crypto
.createHash("sha256")
.update(verifier)
.digest("base64url");
return { verifier, challenge };
}
// Step 1: Start authorization — redirect user to provider
app.get("/auth/login", (req, res) => {
const state = crypto.randomBytes(16).toString("hex");
const { verifier, challenge } = generatePKCE();
// Store in session for verification on callback
req.session.oauthState = state;
req.session.codeVerifier = verifier;
const params = new URLSearchParams({
client_id: OAUTH_CONFIG.clientId,
redirect_uri: OAUTH_CONFIG.redirectUri,
response_type: "code",
scope: OAUTH_CONFIG.scopes.join(" "),
state: state,
code_challenge: challenge,
code_challenge_method: "S256",
access_type: "offline", // Request refresh token
prompt: "consent",
});
res.redirect(`${OAUTH_CONFIG.authorizationEndpoint}?${params}`);
});
// Step 2: Handle callback — verify state and exchange code for tokens
app.get("/auth/callback", async (req, res) => {
const { code, state, error } = req.query;
if (error) {
console.error(`OAuth error: ${error}`);
return res.redirect("/auth/error");
}
// CSRF protection: verify state matches
if (state !== req.session.oauthState) {
console.error("State mismatch — possible CSRF attack");
return res.status(403).send("Invalid state parameter");
}
try {
const tokenResponse = await fetch(OAUTH_CONFIG.tokenEndpoint, {
method: "POST",
headers: { "Content-Type": "application/x-www-form-urlencoded" },
body: new URLSearchParams({
grant_type: "authorization_code",
code: code,
redirect_uri: OAUTH_CONFIG.redirectUri,
client_id: OAUTH_CONFIG.clientId,
code_verifier: req.session.codeVerifier,
}),
});
if (!tokenResponse.ok) {
const err = await tokenResponse.json();
throw new Error(`Token exchange failed: ${err.error_description || err.error}`);
}
const tokens = await tokenResponse.json();
// Store tokens securely in session (server-side)
req.session.accessToken = tokens.access_token;
req.session.refreshToken = tokens.refresh_token;
req.session.tokenExpiry = Date.now() + tokens.expires_in * 1000;
// Clean up PKCE and state from session
delete req.session.oauthState;
delete req.session.codeVerifier;
res.redirect("/dashboard");
} catch (err) {
console.error("Token exchange error:", err.message);
res.redirect("/auth/error");
}
});
// Token refresh middleware
async function ensureValidToken(req, res, next) {
if (!req.session.accessToken) {
return res.redirect("/auth/login");
}
// Refresh if token expires within 60 seconds
if (Date.now() > req.session.tokenExpiry - 60000) {
try {
const refreshResponse = await fetch(OAUTH_CONFIG.tokenEndpoint, {
method: "POST",
headers: { "Content-Type": "application/x-www-form-urlencoded" },
body: new URLSearchParams({
grant_type: "refresh_token",
refresh_token: req.session.refreshToken,
client_id: OAUTH_CONFIG.clientId,
}),
});
if (!refreshResponse.ok) throw new Error("Refresh failed");
const tokens = await refreshResponse.json();
req.session.accessToken = tokens.access_token;
req.session.tokenExpiry = Date.now() + tokens.expires_in * 1000;
// Handle refresh token rotation
if (tokens.refresh_token) {
req.session.refreshToken = tokens.refresh_token;
}
} catch {
// Refresh token is invalid — user must re-authenticate
req.session.destroy();
return res.redirect("/auth/login");
}
}
next();
}
app.get("/dashboard", ensureValidToken, async (req, res) => {
const profile = await fetch("https://www.googleapis.com/oauth2/v2/userinfo", {
headers: { Authorization: `Bearer ${req.session.accessToken}` },
});
const user = await profile.json();
res.json({ message: `Welcome, ${user.name}` });
});
app.listen(3000);import os
import time
import threading
import requests
class ClientCredentialsAuth:
"""OAuth 2.0 client credentials flow for server-to-server auth.
Manages token lifecycle with thread-safe caching and automatic refresh.
"""
def __init__(self, token_endpoint: str, client_id: str, client_secret: str,
scopes: list[str] | None = None):
self.token_endpoint = token_endpoint
self.client_id = client_id
self.client_secret = client_secret
self.scopes = scopes or []
self._access_token: str | None = None
self._token_expiry: float = 0
self._lock = threading.Lock()
def get_access_token(self) -> str:
"""Get a valid access token, refreshing if necessary."""
with self._lock:
if self._access_token and time.time() < self._token_expiry - 60:
return self._access_token
return self._fetch_new_token()
def _fetch_new_token(self) -> str:
response = requests.post(
self.token_endpoint,
data={
"grant_type": "client_credentials",
"client_id": self.client_id,
"client_secret": self.client_secret,
"scope": " ".join(self.scopes),
},
headers={"Content-Type": "application/x-www-form-urlencoded"},
timeout=10,
)
response.raise_for_status()
token_data = response.json()
self._access_token = token_data["access_token"]
self._token_expiry = time.time() + token_data.get("expires_in", 3600)
return self._access_token
def authorized_request(self, method: str, url: str, **kwargs) -> requests.Response:
"""Make an HTTP request with automatic bearer token injection."""
token = self.get_access_token()
headers = kwargs.pop("headers", {})
headers["Authorization"] = f"Bearer {token}"
return requests.request(method, url, headers=headers, **kwargs)
# Usage
auth = ClientCredentialsAuth(
token_endpoint="https://auth.example.com/oauth/token",
client_id=os.environ["M2M_CLIENT_ID"],
client_secret=os.environ["M2M_CLIENT_SECRET"],
scopes=["read:data", "write:data"],
)
# Token is fetched automatically and cached
response = auth.authorized_request("GET", "https://api.example.com/v1/reports")
print(response.json())
# Subsequent calls reuse the cached token until it nears expiry
response = auth.authorized_request("POST", "https://api.example.com/v1/exports", json={
"format": "csv",
"date_range": "2024-01-01/2024-12-31",
})
print(f"Export started: {response.json()['export_id']}")invalid_grant, destroy the session and redirect the user to re-authenticate. Do not retry indefinitely.© seb1n, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in api-and-integration/oauth-2-0-setup of seb1n/awesome-ai-agent-skills.
Open the folder on GitHubat commit 75865a5
OAuth 2 0 Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| OAuth 2 0 Setup this skillseb1n/awesome-ai-agent-skills | 206 | — | ~3.6k | Automated safety check: Pass | MIT | |
| Fortify Developmentcoollabsio/coolify | 63k | 4 repos | ~1.9k | Automated safety check: Pass | MIT | |
| OmniRoute Provider Managementdiegosouzapw/OmniRoute | 74k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Antipattern Preventiondoorkeeper-gem/doorkeeper | 5.5k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Cognitoitsmostafa/aws-agent-skills | 1.2k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Notion Worker Third-Party Auth Guidemakenotion/workers-template | 439 | 1 repos | ~3.5k | Automated safety check: Notes | MIT |
coollabsio/coolify
ACTIVATE when the user works on authentication in Laravel. An agent skill from coollabsio/coolify.
diegosouzapw/OmniRoute
Manages AI provider connections, API keys, OAuth flows and connection tests through OmniRoute's REST API across its 327-provider catalog.
doorkeeper-gem/doorkeeper
Avoid common Ruby and Rails antipatterns that degrade maintainability and performance.
itsmostafa/aws-agent-skills
AWS Cognito user authentication and authorization service. An agent skill from itsmostafa/aws-agent-skills.
makenotion/workers-template
Decides whether a Notion Worker should use a brokered credential, a plaintext environment secret, or OAuth to authenticate against a non-Notion service.
kanchengw/cnllm
Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…
seb1n/awesome-ai-agent-skills
Plan, execute, document, and retest authorized security assessments of AI agents and multi-agent workflows using safe adversarial cases, synthetic identities, canaries, and evidence-based findings.
seb1n/awesome-ai-agent-skills
Build a preliminary, evidence-based EU AI Act readiness assessment across AI-system inventory, territorial scope, operator roles, prohibited-practice screening, risk classification, transparency…
seb1n/awesome-ai-agent-skills
Design and verify auditable human oversight, approval gates, escalation paths, and safe state transitions for AI agent workflows.
seb1n/awesome-ai-agent-skills
Design, implement, harden, and verify Model Context Protocol (MCP) servers with precise tool contracts, least-privilege authorization, safe transports, structured errors, and interoperability tests.
seb1n/awesome-ai-agent-skills
Inspect, extract, OCR, create, merge, split, reorder, rotate, annotate, fill, redact, compress, secure, and verify PDF documents while preserving source files and visual fidelity.
seb1n/awesome-ai-agent-skills
Audit agent skills, plugins, prompts, manifests, scripts, dependencies, and bundled assets for provenance, prompt-injection, permission, execution, exfiltration, persistence, and update risk.
Categories
Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. OAuth 2 0 Setup is an agent skill from seb1n/awesome-ai-agent-skills.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration.
OAuth 2 0 Setup fits situations like: the user requests oauth 2 0 setup; provides relevant inputs for this workflow.
Run `npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a claude-code`. Or copy the skill folder (api-and-integration/oauth-2-0-setup in seb1n/awesome-ai-agent-skills) into .claude/skills/oauth-2-0-setup in your project. Claude Code loads it when a task matches its description.
Run `npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a codex`. Or copy the skill folder (api-and-integration/oauth-2-0-setup in seb1n/awesome-ai-agent-skills) into .agents/skills/oauth-2-0-setup in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add seb1n/awesome-ai-agent-skills --skill oauth-2-0-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/oauth-2-0-setup, .gemini/skills/oauth-2-0-setup, .github/skills/oauth-2-0-setup and .opencode/skills/oauth-2-0-setup in your project.
Going by SKILL.md and its folder, OAuth 2 0 Setup needs credentials named SESSION_SECRET and M2M_CLIENT_SECRET. Our summary lists: Python 3; Node.js; A credential in SESSION_SECRET; A credential in M2M_CLIENT_SECRET.
SKILL.md names 3 domains. In commands or code: accounts.google.com, oauth2.googleapis.com and googleapis.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
OAuth 2 0 Setup is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.6k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with OAuth 2 0 Setup: Fortify Development (coollabsio/coolify, 63k stars), OmniRoute Provider Management (diegosouzapw/OmniRoute, 74k stars), Antipattern Prevention (doorkeeper-gem/doorkeeper, 5.5k stars) and Cognito (itsmostafa/aws-agent-skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
seb1n (a GitHub user) maintains it in seb1n/awesome-ai-agent-skills, which has 206 GitHub stars. The repository holds 101 skills in this directory. The repository was last updated on August 9, 2026.
Source: seb1n/awesome-ai-agent-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.