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 jeremylongworth-source/AgentSkills --skill auth-flow-designgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/auth-flow-design)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/auth-flow-design"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/auth-flow-design/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/jeremylongworth-source/agentskills/auth-flow-design"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/auth-flow-design.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.00342 |
| Opus 5 | $0.00026 | $0.00171 |
| Sonnet 5 | $0.00010 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
auth-flow-design 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.
What it actually says
Auth Flow Design
Core Workflow
- Identify actors, clients, trust boundaries, data sensitivity, and existing identity provider or auth stack.
- Separate authentication, authorization, session/token handling, and audit requirements.
- Define flows for login, token issuance, refresh, logout/revocation, service access, permission checks, and failure behavior.
- Specify where checks happen: gateway, middleware, service layer, database, or external provider.
- Document abuse cases, least privilege, tenant isolation, and review gates.
- Include tests and operational checks for auth regressions.
Safety Rules
- Do not invent provider-specific behavior without checking current official docs when details matter.
- Do not recommend storing plaintext secrets, long-lived broad tokens, or client-trusted authorization decisions.
- Escalate auth flows involving payments, admin access, customer data, multi-tenant isolation, or regulated data.
Deliverable Shape
For auth flow plans, provide:
- Actors and trust boundaries
- Authentication flow
- Authorization model
- Token/session lifecycle
- Permission checks and enforcement points
- Error behavior and audit events
- Abuse cases and mitigations
- Test plan and review gates
References
- Read
references/auth-flow-design-checklist.mdwhen designing or reviewing backend auth flows.
What ships with it
2 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 · 48 lines · 52 tokens per session scan A fd689b2e1ed9
auth-flow-design is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 6d ago), licensed MIT. It adds 52 tokens to every session and 342 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-31.
Other skills, from other repositories
authos-backend-integration
Secure backend APIs with AuthOS-issued JWTs and the AuthOS Node server adapter. Use when building an API that must verify AuthOS bearer tokens, enforce JWT claims, add Express middleware, validate JWKS keys, or create a backend-owned session after a browser OAuth callback.
authos-device-flow
Implement AuthOS device authorization for CLIs, TVs, and headless apps. Use when requesting device codes, building activation pages, polling /auth/token, handling MFA during device auth, or adding platform admin CLI login through AuthOS.
authos-rbac-control
Manage AuthOS organization members, roles, invitations, SCIM tokens, and capability-based permissions. Use when implementing team administration, custom roles, service access grants, invitation flows, SCIM provisioning, or authorization checks inside an AuthOS tenant.
authos-webhook-integration
Build AuthOS webhook receivers and manage tenant webhook subscriptions. Use when configuring organization webhooks, subscribing to event types, verifying live delivery signatures, testing delivery history, or using @drmhse/authos-node webhook helpers.
authos-service-api-integration
Integrate trusted backend services with AuthOS service API routes using X-Api-Key. Use when listing or managing service users, subscriptions, service metadata, service analytics, or provider-token requests from a server-side application.
authos-platform-deployment
Deploy and configure an AuthOS API instance from source or Docker. Use when setting database backend, JWT signing keys, environment variables, billing provider, SMTP, GeoIP, Docker images, health checks, or production reverse proxy settings.