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.
npx skills add prizmad/agent-skills --skill oauthgit clone --depth 1 https://github.com/prizmad/agent-skillsWrote 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.
[](https://agentmods.dev/skills/prizmad/agent-skills/oauth)<a href="https://agentmods.dev/skills/prizmad/agent-skills/oauth"><img src="https://agentmods.dev/badge/skills/prizmad/agent-skills/oauth/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.
<a href="https://agentmods.dev/skills/prizmad/agent-skills/oauth"><img src="https://agentmods.dev/badge/skills/prizmad/agent-skills/oauth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00052 | $0.01345 |
| Opus 5 | $0.00026 | $0.00673 |
| Sonnet 5 | $0.00010 | $0.00269 |
| Haiku 4.5 | $0.00005 | $0.00135 |
Grade A, and why
oauth scanned grade A with 1 finding 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 8d ago.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://prizmad.com/oauth/token \ How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prizmad OAuth 2.1
Prizmad publishes a full OAuth 2.1 authorization server with Dynamic Client Registration. Three grant types are supported, each for a different audience:
| Grant | When | Output |
|---|---|---|
authorization_code (PKCE S256, public client) |
Interactive MCP / connector flow — Claude Desktop, Claude.ai, ChatGPT, Cursor, Zed | RS256 JWT, audience https://prizmad.com/api/mcp, 1 h, refresh-rotated |
refresh_token |
Companion to authorization_code | Same shape; old refresh is single-use, reuse revokes the chain |
client_credentials |
Headless / server-to-server using an API key as client_secret |
HS256 JWT, audience https://prizmad.com/api, 1 h |
The MCP server also accepts the raw API key (przmad_sk_live_...) as a Bearer token directly, without going through OAuth at all.
Discovery
- Authorization server metadata: https://prizmad.com/.well-known/oauth-authorization-server
- Protected resource metadata: https://prizmad.com/.well-known/oauth-protected-resource
- JWKS: https://prizmad.com/.well-known/jwks.json
Authorization Code + PKCE (the "Connect" flow)
This is what runs when a user clicks Add custom connector → enter https://prizmad.com/api/mcp in Claude Desktop, Claude.ai, ChatGPT, Cursor, etc. The client implements RFC 7591 / 8414 / 9728 / 7636 / 8707; no manual app registration is needed.
1. POST /api/mcp without auth
← 401 + WWW-Authenticate: Bearer resource_metadata="…"
2. GET /.well-known/oauth-protected-resource
GET /.well-known/oauth-authorization-server
3. POST /oauth/register
Body (RFC 7591):
{
"client_name": "<your app>",
"redirect_uris": ["<your callback URL>"],
"grant_types": ["authorization_code", "refresh_token"],
"response_types": ["code"],
"token_endpoint_auth_method": "none"
}
← 201 { "client_id": "mcp_…", … } (no client_secret — public client)
4. Browser to /oauth/authorize?
response_type=code
& client_id=<from step 3>
& redirect_uri=<from step 3>
& code_challenge=<S256(verifier)>
& code_challenge_method=S256
& scope=videos:read videos:write
& resource=https://prizmad.com/api/mcp
& state=<csrf>
User signs in (NextAuth) and approves on the consent screen.
← 302 redirect_uri?code=…&state=…
5. POST /oauth/token
grant_type=authorization_code
code=<from step 4>
redirect_uri=<from step 3>
client_id=<from step 3>
code_verifier=<original PKCE verifier>
resource=https://prizmad.com/api/mcp
← 200 { "access_token": "<RS256 JWT>", "refresh_token": "…", "expires_in": 3600, "token_type": "Bearer" }
6. POST /api/mcp with Authorization: Bearer <access_token>
← MCP traffic.
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.
- 8d ago First seen · 138 lines · 52 tokens per session scan A 84e5ac3f9f62
oauth is a skill published in the GitHub repository prizmad/agent-skills (2 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 1,345 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
omni-mcp
Connect to the OmniRoute MCP server (110 tools, 3 transports: SSE/stdio/HTTP). Covers routing, cache, compression, memory, skills, providers, and audit tools across 33 permission scopes.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.