Copy this request to your Agent. It includes the canonical Skill page and manifest.
Agent request
Review the Skillstore skill "auth-implementation-patterns" from https://skillstore.io/skills/wshobson-auth-implementation-patterns.md and its manifest at https://skillstore.io/api/skills/wshobson-auth-implementation-patterns/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.
Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
The static shell, environment, sensitive file, and reconnaissance findings are false positives caused by Markdown fences and non-executed TypeScript examples. No prompt injection or malicious exfiltration intent was found. One content-level issue remains: the OAuth example places an access token in a URL query string.
The OAuth example redirects the access token in the URL query string. Access tokens in URLs can leak through browser history, server logs, analytics, and referrer headers.
Line 345 explicitly appends tokens.accessToken to the callback URL. This is a recognized OAuth implementation risk, although it appears to be insecure guidance rather than malicious intent.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Implement access tokens, refresh tokens, verification middleware, and logout behavior for an API.
Design Authorization Rules
Map roles, permissions, and resource ownership checks before exposing protected endpoints.
Review Auth Security
Compare an existing authentication flow against recommended token, session, cookie, and rate limit controls.
Try These Prompts
Choose an Auth Strategy
Help me choose between session authentication, JWT, and OAuth2 for my application. Ask about my stack, clients, deployment model, and security needs.
Implement JWT Login
Use this skill to design a JWT login flow with short-lived access tokens, hashed refresh tokens, token revocation, and Express middleware.
Add RBAC and Ownership Checks
Use this skill to define roles, permissions, middleware, and ownership checks for these routes. Include denial cases and tests to cover authorization failures.
Audit an Existing Auth Flow
Review my authentication and authorization design against this skill. Identify token, session, OAuth2, password, rate limiting, and RBAC risks with prioritized fixes.
Best Practices
Use short-lived access tokens and store refresh tokens with hashing and revocation support.
Enforce authorization on the server for every protected route and resource operation.
Protect authentication endpoints with rate limits, strong password hashing, and secure cookies when sessions are used.
Avoid
Do not rely on client-side role checks as the only authorization control.
Do not store passwords, refresh tokens, or session secrets in plaintext.
Do not place long-lived access tokens in browser-visible URLs or unsafe storage.
Frequently Asked Questions
Does this skill generate a complete auth service?
No. It provides patterns and examples that must be adapted to your application, database, and threat model.
Can I use it with Claude, Codex, and Claude Code?
Yes. The skill is compatible with Claude, Codex, and Claude Code workflows.
Does it cover both authentication and authorization?
Yes. It covers identity verification, tokens, sessions, OAuth2, roles, permissions, and resource ownership checks.
Is it limited to Node.js applications?
The examples use TypeScript and Express, but the architectural patterns can guide other backend stacks.
Does it include password security guidance?
Yes. It includes password validation, bcrypt hashing, login rate limiting, and common password handling pitfalls.
Should I still run a security review?
Yes. Use this skill as implementation guidance, then perform threat modeling, testing, and compliance review for production systems.