Borrowing it
Nothing to install: this file belongs to qauth-labs/qauth. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/qauth-labs/qauth/main/.claude/skills/auth-oauth/SKILL.mdgit clone --depth 1 https://github.com/qauth-labs/qauthWrote 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/qauth-labs/qauth/auth-oauth)<a href="https://agentmods.dev/skills/qauth-labs/qauth/auth-oauth"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/auth-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/qauth-labs/qauth/auth-oauth"><img src="https://agentmods.dev/badge/skills/qauth-labs/qauth/auth-oauth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 359 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00059 | $0.03279 |
| Opus 5.5 | $0.00024 | $0.01312 |
| Sonnet 5.5 | $0.00012 | $0.00656 |
| Haiku 4.5 | $0.00006 | $0.00328 |
Grade A, and why
auth-oauth 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 1mo 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.
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.
How it starts
The opening of the file, as written. The whole thing — 381 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OAuth 2.0 / 2.1 (Auth)
Standards-aligned OAuth implementation and review. Follow RFC 6749 (core), RFC 9700 (security BCP, Jan 2025), RFC 7636 (PKCE), and OAuth 2.1 draft where applicable.
Standards Quick Reference
| Document | Purpose |
|---|---|
| RFC 6749 | OAuth 2.0 Authorization Framework (core) |
| RFC 6750 | Bearer Token Usage |
| RFC 7636 | PKCE (Proof Key for Code Exchange) |
| RFC 8414 | Authorization Server Metadata |
| RFC 9126 | Pushed Authorization Requests (PAR) |
| RFC 9207 | Authorization Server Issuer Identification |
| RFC 9449 | DPoP (Demonstrating Proof of Possession) |
| RFC 9700 | OAuth 2.0 Security BCP (Jan 2025) |
| OAuth 2.1 draft | Consolidates BCP; PKCE mandatory, implicit/password grant removed |
For detailed RFC/BCP excerpts and links, see reference.md.
Grant Types (What to Use / Avoid)
| Grant | Use? | Notes |
|---|---|---|
| Authorization code + PKCE | ✅ Required | All clients (public and confidential). PKCE mandatory (RFC 9700, OAuth 2.1). |
| Client credentials | ✅ M2M | Confidential clients only. Machine-to-machine flows. |
| Refresh token | ✅ Long-lived | Bind to client; use rotation + sender-constraining. |
Implicit (response_type=token) |
❌ Forbidden | Deprecated; tokens leak via URL/fragment/history. |
| Resource owner password | ❌ Forbidden | Exposes credentials to client (RFC 9700 §2.4). |
What ships with it
1 file 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.
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.
- 1mo ago First seen · 381 lines · 59 tokens per session scan A 5235f2e33642
auth-oauth is a skill published in the GitHub repository qauth-labs/qauth (26 stars, last pushed today), licensed Apache-2.0. It adds 59 tokens to every session and 3,279 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
theauth
Install and use theAuth (@glinr/theauth), the TypeScript auth SDK for AI agents and humans. Use when adding agent identity, scoped permissions, delegation, audit logs, human sign-in plugins, or an MCP OAuth 2.1 authorization server to a Node, Bun, Deno or edge project.
crudauth
Use when building or modifying authentication in a FastAPI app with crudauth (the crudauth PyPI package) — covers CRUDAuth, the AuthUserMixin / makeauthidentity user model, IdentityConfig, currentuser(...) gates, session + bearer transports, OAuth (Google/GitHub), email verification / password reset / change, custom…
nextjs-authentication
Secure token storage (HttpOnly Cookies) and Middleware patterns. Use when implementing authentication, secure session storage, or auth middleware in Next.js.
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.
coding-directives
Implement or review caddy-security Go code, Caddy modules, parsers, lifecycle, and HTTP delegation. Use for app/plugin boundaries, authcrunch integration, errors, logging, and code conventions.
configuration-authentication-cookies
Configure portal cookie names, prefixes, domains, paths, attributes, and refresh overrides. Use for cookie precedence and coordination with authorization token discovery.