Auth Flow Design
Design authentication and authorization flows for backend APIs and applications. Use when Codex is asked to plan login, sessions, tokens, roles, permissions, OAuth/OIDC, API keys, service accounts, tenant access, or auth-related error behavior.
Install
$ agentstack add skill-jeremylongworth-source-agentskills-auth-flow-design ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-jeremylongworth-source-agentskills-auth-flow-design) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: jeremylongworth-source
- Source: jeremylongworth-source/AgentSkills
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.