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.
npx skills add launch52-ai/flutter-template --skill authgit clone --depth 1 https://github.com/launch52-ai/flutter-templateWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/launch52-ai/flutter-template/auth)<a href="https://agentmods.dev/skills/launch52-ai/flutter-template/auth"><img src="https://agentmods.dev/badge/skills/launch52-ai/flutter-template/auth/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/launch52-ai/flutter-template/auth"><img src="https://agentmods.dev/badge/skills/launch52-ai/flutter-template/auth.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00048 | $0.01603 |
| Opus 5.5 | $0.00019 | $0.00641 |
| Sonnet 5.5 | $0.00010 | $0.00321 |
| Haiku 4.5 | $0.00005 | $0.00160 |
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 1mo 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.
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
/coreskill 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
- Backend type: Supabase or Custom API?
- Auth methods: (multi-select) Social Login, Phone OTP, Email/Password
- 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
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- checklist.md 6.6 KB
- implementation-guide.md 14 KB
- reference/failures/auth_failures.dart 4.3 KB
- reference/models/auth_result.dart 2.9 KB
- reference/models/user_profile.dart 3.3 KB
- reference/providers/auth_provider.dart 9.6 KB
- reference/providers/auth_state.dart 3.2 KB
- reference/repositories/auth_repository_impl.dart 4.3 KB
- reference/repositories/auth_repository.dart 3.2 KB
- reference/repositories/mock_auth_repository.dart 5.4 KB
- reference/screens/login_screen.dart 6.7 KB
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.
- 1mo ago First seen · 210 lines · 48 tokens per session scan A aa0aa5a55f5f
auth is a skill published in the GitHub repository launch52-ai/flutter-template (2 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 1,603 once invoked, about $0.0002 per session on Opus 5.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.
Other skills, from other repositories
django-celery-expert
Expert Django Celery guidance for asynchronous task processing. Use when designing background tasks, configuring Celery workers, handling task retries and errors, optimizing Celery performance, implementing periodic tasks with Celery Beat, or setting up production monitoring for Celery. Do not use for general Django…
django-expert
Expert Django backend development guidance. Use when creating Django models, views, serializers, or APIs; debugging ORM queries or migrations; optimizing database performance; implementing authentication; writing tests; or working with Django REST Framework. Follows Django best practices and modern patterns.
nodejs-backend-patterns
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
nodejs-best-practices
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
upgrade-stripe
Guide for upgrading Stripe API versions and SDKs.
writing-blogs
Writes, structures, and formats SEO-optimized blog posts for the Appwrite blog following established conventions for voice, tone, frontmatter, and post structure. Use when the user asks to write, draft, create, or outline a blog post, or when working with files in src/content/blog/posts/.