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 pledgeandgrow/pledge-skills --skill auth0git clone --depth 1 https://github.com/pledgeandgrow/pledge-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/pledgeandgrow/pledge-skills/auth0)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/auth0"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/auth0/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/pledgeandgrow/pledge-skills/auth0"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/auth0.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.00032 | $0.05868 |
| Opus 5 | $0.00016 | $0.02934 |
| Sonnet 5 | $0.00006 | $0.01174 |
| Haiku 4.5 | $0.00003 | $0.00587 |
Grade A, and why
auth0-docs 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 9d 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth0 Skill
Auth0 — Identity platform for authentication, authorization, and user management. Version: Latest | Docs: auth0.com/docs
Quick Reference
| Topic | File | Sections |
|---|---|---|
| Getting Started | getting-started.md |
Overview, identity fundamentals, quickstarts, configure Auth0, auth flows, architecture |
| Authentication | authentication.md |
Universal Login, passwordless, identity providers (social/enterprise/database), protocols (OAuth 2.0, OIDC, SAML), custom token exchange, sessions, cookies |
| Customize & Secure | customize-secure.md |
Branding, login pages, custom domains, emails, Actions, Rules, Hooks, Forms, tokens (ID/Access/Refresh/JWT), MFA, attack protection, compliance |
| Manage & Deploy | manage-deploy.md |
User accounts, metadata, migration, search, organizations, RBAC, APIs, SDKs, CLI, Terraform, deployment, monitoring, logs, AI |
Core Concepts
- Tenant: Auth0 account with unique domain (
yourtenant.auth0.com) - Application: Client app (SPA, Web, Native, M2M) registered with Auth0
- API: Protected resource server with scopes
- Connection: Identity source (database, social, enterprise, passwordless)
- Universal Login: Auth0-hosted authentication pages (recommended)
- Token: Credential after authentication (ID Token, Access Token, Refresh Token)
- Action: Custom Node.js code executed during auth flows (replaces Rules/Hooks)
- Organization: B2B customer grouping with per-org connections and branding
- Scope: Permission granted to a client app (e.g.,
read:items)
Authentication Flows
| Flow | Use Case |
|---|---|
| Authorization Code Flow | Server-side web apps |
| Authorization Code Flow with PKCE | SPAs, mobile apps |
| Client Credentials Flow | Machine-to-machine |
| Device Authorization Flow | Input-constrained devices |
| Resource Owner Password Flow | Highly-trusted apps (not recommended) |
| Implicit Flow with Form Post | Legacy SPAs (deprecated) |
| Hybrid Flow | Need ID token immediately + code exchange |
| CIBA | Backchannel-initiated authentication |
| Custom Token Exchange (RFC 8693) | Token swapping, delegation |
What ships with it
4 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.
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.
- 9d ago First seen · 405 lines · 32 tokens per session scan A 3cdda616abba
auth0-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 5,868 once invoked, about $0.0002 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-31.
Other skills, from other repositories
identity-access-expert
Design authentication and authorisation: OAuth 2.1 and OpenID Connect, session and token handling, RBAC and ABAC, and multi-tenant access control. Use when the user mentions OAuth, OIDC, SAML, SSO, JWT, refresh tokens, PKCE, login flows, sessions, roles and permissions, RBAC or ABAC, or when the task involves securing…
configuring-oauth2-authorization-flow
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.
configuring-oauth2-authorization-flow
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0…
security-patterns
Security patterns for authentication, defense-in-depth, input validation, OWASP Top 10, LLM safety, and PII masking. Use when implementing auth flows, security layers, input sanitization, vulnerability prevention, prompt injection defense, or data redaction.
auth-patterns
Use when implementing authentication (JWT, sessions, OAuth), authorization (RBAC, ABAC), password hashing, MFA, or security best practices for backend services.
testing-oauth2-implementation-flaws
Tests OAuth 2.0 and OpenID Connect implementations for security flaws including authorization code interception, redirect URI manipulation, CSRF in OAuth flows, token leakage, scope escalation, and PKCE bypass. The tester evaluates the authorization server, client application, and token handling for common…