auth-stinger — Claude Code skill: what it does, how to install
auth-stinger guides authentication architecture, provider choice, sessions, RBAC, and OAuth verification under strict security baselines.
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-stinger does
The skill inspects package.json and .env.example to detect runtimes such as Next.js, Remix, Vite, Express, or Fastify. It evaluates whether a project needs hosted services like Clerk, self-hosted libraries like Better Auth, or Supabase Auth, producing decision records and migration blueprints.
It enforces explicit security rules across the application. Session cookies require HttpOnly, Secure, and SameSite=Lax, while access control checks must live in middleware and data layers simultaneously. For Google OAuth, it insists on Google Identity Services over legacy gapi.auth2 and accounts for Google client deletion rules.
The skill rejects SMS as a primary MFA factor because of SIM-swap attacks, relegating it to recovery workflows only.
What it helps with
- select an authentication vendor across B2B and B2C constraints
- configure session cookies and refresh token rotation schemes
- prepare scope justifications for Google OAuth verification
- outline migrations between auth libraries without session invalidation
Example prompts for the agent
- Evaluate Clerk versus Better Auth for our Fastify and React project
- Configure Google sign-in using Google Identity Services and draft scope requirements
- Audit the session cookie storage and role checks before deployment
How to install auth-stinger
1Plugin marketplace
/plugin marketplace add legioncodeinc/vibe-coding-tools/plugin install platform-and-release-tools@wasp-nestThis installs the whole platform-and-release-tools plugin with all its skills
2Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill auth-stinger -a claude-code3Manually: put the files in place
~/.claude/skills/auth-stinger/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/auth-stinger/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill auth-stinger -a codex2Manually: put the files in place
.agents/skills/auth-stinger/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill auth-stinger -a cursor2Manually: put the files in place
.cursor/skills/auth-stinger/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install legioncodeinc/vibe-coding-tools plugins/platform-and-release-tools/skills/auth-stinger2Manually: put the files in place
.github/skills/auth-stinger/SKILL.md1Skills CLI (Vercel)
npx skills add legioncodeinc/vibe-coding-tools --skill auth-stinger -a gemini-cli2Platform CLI
gemini skills install https://github.com/legioncodeinc/vibe-coding-tools --path plugins/platform-and-release-tools/skills/auth-stingerManually: put the files in place
.devin/skills/auth-stinger/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about auth-stinger
How to install auth-stinger in Claude Code?
Run /plugin marketplace add legioncodeinc/vibe-coding-tools, then execute /plugin install platform-and-release-tools@wasp-nest.
What does auth-stinger do?
It guides authentication architecture decisions, session cookie hardening, account recovery rules, and Google OAuth compliance.
Why does the skill restrict SMS verification?
It classifies SMS as vulnerable to SIM swaps, restricting it strictly to recovery workflows instead of primary multi-factor verification.