auth

A starting structure for adding user sign-in to an app using Clean Architecture, a way of separating app parts by responsibility. It creates shared authentication code that social login and phone-code login features can build on.

In plain words
What is it for?
Starting authentication, defining user profiles and sign-in results, and preparing an app for email/password, social, or phone-code login.
Why use it?
It provides the common sign-in structure first, so each login method does not need to recreate user state, profiles, and sign-out handling.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/launch52-ai/flutter-template/auth
Any agent
npx skills add launch52-ai/flutter-template --skill auth
Clone the repo
git clone --depth 1 https://github.com/launch52-ai/flutter-template

Made for: Claude Code, Codex.

Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,603 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00048 $0.01603
Opus 5 $0.00024 $0.00801
Sonnet 5 $0.00010 $0.00321
Haiku 4.5 $0.00005 $0.00160

Measured 2d ago against content hash aa0aa5a55f5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

auth scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/auth/SKILL.md · 210 lines

How it starts

The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Auth - Base Authentication Scaffold

Creates the authentication feature foundation with Clean Architecture. This skill generates shared infrastructure that /social-login and /phone-auth build upon.

When to Use This Skill

  • After /core skill completes
  • Before adding specific auth methods (/social-login, /phone-auth)
  • Setting up auth from scratch
  • User asks to "add authentication" or "create auth"

Questions to Ask

  1. Backend type: Supabase or Custom API?
  2. Auth methods: (multi-select) Social Login, Phone OTP, Email/Password
  3. User profile fields: Custom fields beyond id/email? (e.g., displayName, avatarUrl)

What This Skill Creates

Base auth infrastructure that specific auth skills extend:

Component Purpose Extended By
AuthRepository Base interface (signOut, getCurrentUser) social-login, phone-auth
AuthNotifier State management with disposal safety All auth screens
AuthState Sealed states (loading, authenticated, error) All auth screens
UserProfile User model All auth methods
AuthResult Sign-in result with isNewUser flag social-login, phone-auth
LoginScreen Base scaffold for auth UI Buttons added by methods
AuthFailure Base failure types Extended by methods

Reference Files

reference/
├── models/           # UserProfile, AuthResult
├── repositories/     # Interface, Supabase impl, mock
├── providers/        # AuthState, AuthNotifier
├── screens/          # LoginScreen scaffold
└── failures/         # Base auth failure types

See: implementation-guide.md for complete file list.

Workflow

Phase 1: Ask Questions

Use AskUserQuestion to gather:

  • Backend type (Supabase vs Custom API)
  • Which auth methods needed
  • Custom user profile fields

Phase 2: Generate Structure

Create standard Clean Architecture feature:

lib/features/auth/
├── data/          # models/, repositories/
├── domain/        # failures/, repositories/
├── presentation/  # providers/, screens/
└── i18n/          # auth.i18n.yaml

Read the full file on GitHub · 210 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 210 lines · 48 tokens per session scan A aa0aa5a55f5f

Subscribe to this mod's changes

auth is a skill published in the GitHub repository launch52-ai/flutter-template (2 stars, last pushed 6mo ago), licensed MIT. It adds 48 tokens to every session and 1,603 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories