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 agentmods add skills/qauth-labs/qauth/auth-oauthnpx skills add qauth-labs/qauth --skill auth-oauthgit 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.svg" alt="Measured on agentmods" 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.00059 | $0.03279 |
| Opus 5 | $0.00030 | $0.01639 |
| Sonnet 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 6d 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.
- 6d 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 (24 stars, last pushed 5d ago), licensed Apache-2.0. It adds 59 tokens to every session and 3,279 once invoked, about $0.0003 per session on Opus 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
update-portal-ui
Guidelines for updating or designing pages in the portal React frontend (portal/src). Covers component conventions, link rendering rules, i18n patterns, and common pitfalls.
api-design
Review or design APIs for Authgear. In review mode, evaluates a design draft against the checklist. In ideation mode, develops a design from a description and self-reviews it.
update-feature-config
Add or change a feature config field/section in pkg/lib/config (authgear.features.yaml). Use when adding a new feature config field, adding a new top-level section, or touching an existing section's Merge implementation.
bootstrap-local-dev
Set up a fresh authgear-server development environment from scratch. Use when onboarding a new contributor, setting up a new machine, or when the user says "set up local dev from scratch" / "first-time setup". Covers the asdf + Homebrew install path on macOS; Nix users should follow CONTRIBUTING.md directly.
add-go-test
Write or extend Go unit tests in this repo. Use when the user asks to add or update Go tests.
review-pr
Produce a structured code review report for the current branch's PR (purpose, API interface changes, code quality, bugs, security, performance), with a mandatory second verification pass. Use when the user asks "what does this PR do", "review this branch/PR", or asks to confirm/double-check review findings and look…