workos-wasp-drone — Claude Code and Codex subagent: AuthKit and WorkOS
workos-wasp-drone — a subagent for WorkOS integration: AuthKit (UI and headless), sealed sessions, User Management, RBAC, SSO (SAML/OIDC), Directory Sync, MFA and migration from Supabase Auth or Clerk.
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 workos-wasp-drone does
workos-wasp-drone is a WorkOS specialist: owns AuthKit (hosted and headless modes), sealed sessions, JWT/JWKS verification, User Management API (users, organizations, memberships, invitations), RBAC model, SSO and Directory Sync, MFA/passkeys/Magic Auth support, webhook signature verification, and migrations from other providers.
The subagent reads your SvelteKit context, confirms the AuthKit mode (hosted or headless) and integration stage, then follows step-by-step guides: mode selection, wiring @workos-inc/authkit-sveltekit, setting up sealed sessions, modeling users and organizations, RBAC layers (route guard and data layer), SSO/SCIM for B2B, webhooks, and migrations. Runs a security checklist before handoff.
Out of scope: provider selection against other auth vendors (routed to auth-wasp-drone), sign-in screen JSX or branding (routed to react-wasp-drone or ux-ui-svelte-stinger), users/organizations schema design (routed to db-wasp-drone), or security audit of the final code (routed to security-wasp-drone).
What it helps with
- wire AuthKit into SvelteKit without exposing refresh tokens
- set up two-layer RBAC: route guards and data queries
- integrate SSO (SAML/OIDC) for B2B customers
- sync users and roles via SCIM Directory Sync
- migrate user base from Supabase Auth or Clerk to WorkOS
Example prompts for the agent
- Hook up AuthKit to our SvelteKit app, show me sealed sessions
- Set up org RBAC: admin, member, viewer with data-layer checks
- Migrate 5000 users from Supabase Auth to WorkOS
How to install workos-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/workos-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/workos-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/workos-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 workos-wasp-drone
How do I install workos-wasp-drone in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then /plugin install platform-and-release-tools@wasp-nest. The subagent loads from .claude/agents/workos-wasp-drone.md.
What does workos-wasp-drone do?
It handles WorkOS: AuthKit setup (hosted or headless), sealed sessions, User Management, RBAC, SSO/SCIM, webhook handling, and migrations from other auth providers. Built for SvelteKit.
Should I use hosted or headless AuthKit?
Hosted is a ready-made sign-in page from WorkOS. Headless means you build the UI and call WorkOS APIs directly. The subagent helps you choose based on your design and requirements.