# 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.

- **Type:** Skill
- **Install:** `agentstack add skill-jeremylongworth-source-agentskills-auth-flow-design`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [jeremylongworth-source](https://agentstack.voostack.com/s/jeremylongworth-source)
- **Installs:** 0
- **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [jeremylongworth-source](https://github.com/jeremylongworth-source)
- **Source:** https://github.com/jeremylongworth-source/AgentSkills/tree/main/skills/auth-flow-design

## Install

```sh
agentstack add skill-jeremylongworth-source-agentskills-auth-flow-design
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Auth Flow Design

## Core Workflow

1. Identify actors, clients, trust boundaries, data sensitivity, and existing
   identity provider or auth stack.
2. Separate authentication, authorization, session/token handling, and audit
   requirements.
3. Define flows for login, token issuance, refresh, logout/revocation, service
   access, permission checks, and failure behavior.
4. Specify where checks happen: gateway, middleware, service layer, database, or
   external provider.
5. Document abuse cases, least privilege, tenant isolation, and review gates.
6. 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.md` when 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](https://github.com/jeremylongworth-source)
- **Source:** [jeremylongworth-source/AgentSkills](https://github.com/jeremylongworth-source/AgentSkills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-jeremylongworth-source-agentskills-auth-flow-design
- Seller: https://agentstack.voostack.com/s/jeremylongworth-source
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.