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 agentmods add skills/fullstack-phoenix/saas_kit/require-confirmed-usernpx skills add fullstack-phoenix/saas_kit --skill require-confirmed-usergit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWhat 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 | $0.00043 | $0.00982 |
| Opus 5 | $0.00022 | $0.00491 |
| Sonnet 5 | $0.00009 | $0.00196 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
require-confirmed-user 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Require Confirmed User
Adds an email-confirmation gate: any authenticated user whose confirmed_at is
nil is redirected to /users/confirm until they confirm their email. Ships a
confirmation-pending LiveView with a resend button that sends the magic-link
login (which confirms the account on click). OAuth sign-ins are auto-confirmed
and skip the gate, so in practice this guards edge cases (admin impersonation,
manually created users) and adds defense-in-depth.
When to use
- The app needs to block unconfirmed users from authenticated pages until they verify their email.
- You want a ready-made "confirm your email" page with a resend button.
- Don't reach for this if every sign-in path already confirms the user (e.g. OAuth-only apps) — the gate would never fire.
Dependencies
- Requires: None. But it patches
lib/my_app_web/user_auth.exand assumesauthenticationis installed (it edits therequire_authenticated_userpipeline). Installauthenticationfirst. - Recommended: None. Usually installed via the
authenticationinstaller'semail_confirmationdecision.
Install
mix saaskit.feature.install require_confirmed_user
No decisions are asked. The installer injects the gate into the auth pipeline,
adds the ensure_confirmed_user/1 helper, generates the confirmation-pending
LiveView, and registers the /users/confirm route.
What it generates
lib/my_app_web/live/user_live/confirmation_pending.ex— theConfirmationPendingLiveView. Redirects already-confirmed users to the signed-in path; otherwise shows a resend button.- Patches
lib/my_app_web/user_auth.ex:- Pipes
require_authenticated_user/2throughensure_confirmed_user/1. - Adds the private
ensure_confirmed_user/1that redirects to~p"/users/confirm"with a flash whenuser.confirmed_atis nil.
- Pipes
- Patches
lib/my_app_web/router.ex— adds a:require_confirmationlive_session(on_mount:ensure_authenticated) routing/users/confirmtoUserLive.ConfirmationPending.
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.
- 2d ago First seen · 109 lines · 43 tokens per session scan A 1adf1c75e6bb
require-confirmed-user is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 43 tokens to every session and 982 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.