auth-implementation-patterns skill
✓ VerifiedImplement secure access control systems using JWT, OAuth2, session management, and RBAC patterns.
- GitHub stars
- 42,413
- Files
- 2
- Last commit
- Nov 9, 2026
- License
- MIT
- Allowed tools
- —
What does the auth-implementation-patterns skill do?
auth-implementation-patterns is an agent skill. Implement secure access control systems using JWT, OAuth2, session management, and RBAC patterns.
Summary generated from the skill's SKILL.md.
About the auth-implementation-patterns skill
Building secure access control systems and managing user identities is the primary function of this skill. Developers use it to implement authentication and authorization strategies such as JWT, OAuth2, session management, and role-based access control (RBAC). It serves as a guide for securing REST or GraphQL APIs, designing multi-tenancy architectures, or migrating existing authentication systems.
An agent should load this skill when a project requires identity verification or permission checking. It provides guidance on technical implementations like using bcrypt or argon2 for password hashing, setting httpOnly and secure flags for cookies, and managing short-lived access tokens. The skill also helps identify common security mistakes, such as storing JWTs in localStorage or relying solely on client-side authorization checks. For more in-depth technical guidance, the skill points to detailed documentation located in the references/details.md file.
What an agent can do with it
- 1Securing API endpointsAn agent can help you design and implement security measures for REST or GraphQL APIs.
- 2Implementing role-based permissionsYou can use this to set up systems that control what specific users are allowed to do within an application.
- 3Integrating social loginsUse this skill to add OAuth2 or social login capabilities like Google or GitHub to your software.
- 4Debugging security vulnerabilitiesAn AI client can assist in identifying and fixing common authentication and authorization errors.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the auth-implementation-patterns skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the auth-implementation-patterns skill in Plugin
/plugin marketplace add wshobson/agents /plugin install developer-essentials@claude-code-workflows
Install the auth-implementation-patterns skill in Claude Code
~/.claude/skills/auth-implementation-patterns/SKILL.md
$ npx degit wshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns ~/.claude/skills/auth-implementation-patternsInstall the auth-implementation-patterns skill in Claude Code (project)
.claude/skills/auth-implementation-patterns/SKILL.md
$ npx degit wshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns .claude/skills/auth-implementation-patternsInstall the auth-implementation-patterns skill in Codex
~/.agents/skills/auth-implementation-patterns/SKILL.md
$ npx degit wshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns ~/.agents/skills/auth-implementation-patternsInstall the auth-implementation-patterns skill in Gemini CLI
~/.gemini/skills/auth-implementation-patterns/SKILL.md
$ npx degit wshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns ~/.gemini/skills/auth-implementation-patternsInstall the auth-implementation-patterns skill in Claude.ai
npx degit wshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns auth-implementation-patterns && zip -r auth-implementation-patterns.zip auth-implementation-patterns # claude.ai → Customize → Skills → + → Create skill → Upload a skill → auth-implementation-patterns.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablewshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns is public and reachablegithub.com/wshobson/agents/tree/HEAD/plugins/developer-essen ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-09github.com/wshobson/agents/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/wshobson/agents/blob/HEAD/plugins/developer-essen ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/wshobson/agents/blob/HEAD/plugins/developer-essen ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 84 linesgithub.com/wshobson/agents/blob/HEAD/plugins/developer-essen ↗Pass
SKILL.md
View on GitHubAuthentication & Authorization Implementation Patterns
Build secure, scalable authentication and authorization systems using industry-standard patterns and modern best practices.
When to Use This Skill
- Implementing user authentication systems
- Securing REST or GraphQL APIs
- Adding OAuth2/social login
- Implementing role-based access control (RBAC)
- Designing session management
- Migrating authentication systems
- Debugging auth issues
- Implementing SSO or multi-tenancy
Core Concepts
1. Authentication vs Authorization
Authentication (AuthN): Who are you?
- Verifying identity (username/password, OAuth, biometrics)
- Issuing credentials (sessions, tokens)
- Managing login/logout
Authorization (AuthZ): What can you do?
- Permission checking
- Role-based access control (RBAC)
- Resource ownership validation
- Policy enforcement
2. Authentication Strategies
Session-Based:
- Server stores session state
- Session ID in cookie
- Traditional, simple, stateful
Token-Based (JWT):
- Stateless, self-contained
- Scales horizontally
- Can store claims
OAuth2/OpenID Connect:
- Delegate authentication
- Social login (Google, GitHub)
- Enterprise SSO
Detailed patterns and worked examples
Detailed pattern documentation lives in references/details.md. Read that file when the navigation tier above is insufficient.
Best Practices
- Never Store Plain Passwords: Always hash with bcrypt/argon2
- Use HTTPS: Encrypt data in transit
- Short-Lived Access Tokens: 15-30 minutes max
- Secure Cookies: httpOnly, secure, sameSite flags
- Validate All Input: Email format, password strength
- Rate Limit Auth Endpoints: Prevent brute force attacks
- Implement CSRF Protection: For session-based auth
- Rotate Secrets Regularly: JWT secrets, session secrets
- Log Security Events: Login attempts, failed auth
- Use MFA When Possible: Extra security layer
Common Pitfalls
- Weak Passwords: Enforce strong password policies
- JWT in localStorage: Vulnerable to XSS, use httpOnly cookies
- No Token Expiration: Tokens should expire
- Client-Side Auth Checks Only: Always validate server-side
- Insecure Password Reset: Use secure tokens with expiration
- No Rate Limiting: Vulnerable to brute force
- Trusting Client Data: Always validate on server
Files in this skill
2auth-implementation-patterns skill questions
How do I install the auth-implementation-patterns skill in Claude Code?
Run npx degit wshobson/agents/plugins/developer-essentials/skills/auth-implementation-patterns ~/.claude/skills/auth-implementation-patterns. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the auth-implementation-patterns skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.