auth-wasp-drone — Claude Code subagent: setup guide
auth-wasp-drone — an authentication implementation subagent for provider choice, OAuth wiring, MFA, RBAC, session handling, and B2B SSO.
AGPL-3.0-or-later ★ 96 updated 2026-10-18
/plugin marketplace add legioncodeinc/vibe-coding-tools
/plugin install platform-and-release-tools@wasp-nestWhat auth-wasp-drone does
auth-wasp-drone covers the implementation side of authentication, from selecting a provider to preparing handoffs for audits and related work. It classifies the product scenario, reviews the runtime and existing auth setup, then produces a provider choice with a reason and one alternative. The supported provider set includes Clerk, Better Auth, Auth.js, Supabase Auth, WorkOS, Stack Auth, Kinde, and Stytch.
For Google OAuth, it checks scope selection, verification work, Google Identity Services migration, and the October 2025 rule that can remove production clients after 6 months without recent traffic. It also defines MFA and passkey enrollment, recovery handling, RBAC across middleware and the data layer, and secure session-cookie settings. New Google OAuth flows need GIS because legacy gapi.auth2 is deprecated. Deliverables can be recorded as an ADR or an auth handoff report.
What it helps with
- choose an authentication provider for a B2C or B2B product
- wire Google OAuth and prepare its verification requirements
- define MFA, passkeys, and account recovery
- enforce roles across a multi-tenant application
- review session storage and cookie attributes
Example prompts for the agent
- Choose an authentication provider for a Next.js app that needs B2B SSO, and explain one alternative.
- Set up Google OAuth with GIS, review the requested scopes, and list the verification work.
- Design RBAC for a multi-tenant app with checks in middleware and the data layer.
How to install auth-wasp-drone
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nest2Manually: put the files in place
.claude/agents/auth-wasp-drone.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/auth-wasp-drone.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/auth-wasp-drone.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about auth-wasp-drone
How do I install auth-wasp-drone in Claude Code?
Run these steps in order: /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install platform-and-release-tools@wasp-nest, then add .claude/agents/auth-wasp-drone.md.
What does auth-wasp-drone do?
It helps implement provider selection, OAuth, MFA, passkeys, RBAC, session storage, and B2B SSO. Auditing the finished implementation, building the React auth UI, and designing the user or session schema are handed off to other subagents.
Why does Google OAuth need GIS?
New Google OAuth flows should use Google Identity Services. Legacy gapi.auth2 is deprecated, and the subagent also accounts for deletion of clients with no recent traffic after 6 months.