swarm-auth-mfa-agent

Audits gnubok authentication and MFA enforcement across hosted and self-­hosted deployments.

209|46|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/erp-mafia/gnubok --skill swarm-auth-mfa-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: swarm-auth-mfa-agent
Source: https://github.com/erp-mafia/gnubok/tree/main/.claude/skills/swarm-auth-mfa-agent
Command: npx skills add https://github.com/erp-mafia/gnubok --skill swarm-auth-mfa-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auditors and security engineers need a structured, read-only lens into gnubok's authentication and authorization flows to identify MFA enforcement gaps, PKCE misconfigurations, API key handling weaknesses, and OAuth 2.1 integration issues across hosted and self-hosted deployments.

Core Features & Use Cases

  • Read-only audit agent focused on authentication and authorization correctness.
  • Sweeps across authentication surfaces: primary login, magic link, MFA enforcement, API keys, OAuth 2.1 for Claude Desktop MCP, cron-based access, and invite tokens.
  • Environment flags handling to ensure MFA gating behavior is consistent across hosted vs self-hosted deployments.
  • Files to sweep include lib/auth/, lib/supabase/middleware.ts, middleware.ts, app/login/, app/register/, app/reset-password/, app/mfa/enroll/, app/mfa/verify/, app/api/mcp-oauth/, app/invite/[token]/
  • Security-focused checks for MFA enforcement, AAL verification, API key scope and rotation, PKCE verification, and invite token handling.
  • Session management considerations and potential misconfigurations (cookie flags, revocation, and device awareness).

Quick Start

Run a read-only audit of gnubok's authentication surfaces to identify MFA bypass paths, AAL2 gaps, and API key/OAuth/token handling weaknesses.

Frequently Asked Questions about swarm-auth-mfa-agent

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

FAQPage Schema
How do I audit MFA enforcement and OAuth 2.1 flows in gnubok?▼

Audit MFA enforcement and OAuth 2.1 flows in gnubok by running a read-only sweep across authentication surfaces like lib/auth, middleware, and API routes to identify AAL2 gaps and token handling issues.

What is the best way to check PKCE verification and API key rotation for self-hosted deployments?▼

Checking PKCE verification and API key rotation for self-hosted deployments involves scanning environment flags and middleware configurations to ensure consistent MFA gating behavior and secure token handling.

How does session management misconfiguration affect gnubok authentication?▼

Session management misconfiguration affects gnubok authentication by exposing weak cookie flags, lacking device awareness, or failing token revocation, which are flagged during read-only security reviews of the authentication surface.

Can I verify AAL2 compliance and OAuth codes for cron-based access?▼

Yes, verifying AAL2 compliance and OAuth codes for cron-based access is possible by sweeping middleware and API routes to ensure strict authentication enforcement across all deployment types.

Does gnubok support read-only security reviews of invite token handling?▼

Yes, gnubok supports read-only security reviews of invite token handling by auditing app/invite routes and related authentication surfaces to flag potential misconfigurations and bypass paths.

Why does MFA bypass occur in magic link and OAuth 2.1 authentication?▼

MFA bypass occurs in magic link and OAuth 2.1 authentication when middleware fails to enforce AAL2 or environment flags are misconfigured, allowing unauthorized access to protected routes.