authentication-patterns

Analyze authentication implementations for security vulnerabilities and compliance.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/marquesfelip/agents-and-skills --skill authentication-patterns-marquesfelip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authentication-patterns
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/authentication-patterns
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill authentication-patterns-marquesfelip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Authentication is foundational to secure software, yet many systems suffer from weak patterns, improper session handling, and MFA gaps that expose credentials and accounts.

Core Features & Use Cases

  • Pattern selection: choose between Session + Cookie, JWT, OAuth2 + OIDC, Passwordless, and MFA patterns based on app type.
  • Secure implementation: provide checklists for credential handling, rate limiting, session management, token hygiene, and MFA enforcement.
  • Vulnerability guidance: identify and mitigate common auth flaws such as brute force, enumeration, and session fixation.
  • Output & review: produce actionable recommendations and an implementation plan.

Quick Start

Evaluate the existing authentication flow and return a recommended pattern with explicit security steps.

Frequently Asked Questions about authentication-patterns

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose the right authentication pattern for my web app?

Choosing an authentication pattern requires evaluating your app type. You can select from Session + Cookie, JWT, OAuth2 + OIDC, Passwordless, or MFA patterns to establish secure logins and reduce common account vulnerabilities.

What is the best way to secure JWT implementations and prevent token vulnerabilities?

Securing JWT implementations requires following token hygiene guidelines. You must analyze your current flow to ensure compliance with credential handling, rate limiting, and session management rules to mitigate brute force and session fixation flaws.

How do I implement secure session management and rate limiting for APIs?

Implementing secure session management involves applying specific checklists for credential handling and rate limiting. Analyzing your API authentication flow ensures token hygiene and compliance, reducing exposure to brute force and session fixation attacks.

Does this approach support passwordless and MFA enforcement across different identity providers?

Yes, this approach supports passwordless and MFA enforcement across various identity providers. Analyzing your implementation ensures MFA guidelines are met, reducing common authentication vulnerabilities and securing user credentials effectively.

How can I identify and mitigate authentication vulnerabilities like user enumeration?

Identifying authentication vulnerabilities requires analyzing your login implementations. You can detect and mitigate common auth flaws like user enumeration, brute force, and session fixation by applying secure credential handling and rate limiting checklists.

When should I use OAuth2 and OIDC instead of session cookies for authentication?

Use OAuth2 and OIDC instead of session cookies when delegating authentication to external identity providers. Analyzing your implementation helps determine the best pattern for your app type, ensuring token hygiene and compliance with security guidelines.