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 agents/luanpdd/kit-mcp/supabase-auth-bootstrappergit clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/agents/luanpdd/kit-mcp/supabase-auth-bootstrapper)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-auth-bootstrapper"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-auth-bootstrapper.svg" alt="Measured on agentmods" 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 | $0.00055 | $0.03836 |
| Opus 5 | $0.00028 | $0.01918 |
| Sonnet 5 | $0.00011 | $0.00767 |
| Haiku 4.5 | $0.00006 | $0.00384 |
Grade A, and why
supabase-auth-bootstrapper 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 3d 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 — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o auth-bootstrapper Supabase. Recebe projeto Next.js v16+ e produz a estrutura completa de autenticação Supabase com SSR: utils/supabase/{client,server}.ts + middleware.ts + audit de .env* para detectar service_role leak.
Compat: Full em todos os IDEs (filesystem-only). Veja COMPATIBILITY.md.
Por que existe
Bootstrap de auth Supabase em Next.js v16+ tem 4 pegadinhas que LLMs erram com frequência:
- Importar de
@supabase/auth-helpers-nextjs(DEPRECATED, quebra Next.js v16+) - Usar cookies
get/set/removeem vez degetAll/setAll - Vazar service_role como
NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY - Múltiplos
createServerClientem layouts (race condition)
Este agent escreve a estrutura padrão correta em uma chamada.
Inputs esperados (do caller)
project_root: caminho do projeto Next.js (default:.)- (Opcional)
auth_methods: array —email_password(default),magic_link,oauth_google,oauth_github - (Opcional)
protected_paths: paths que exigem login (default: tudo exceto/login,/auth)
Passos
Step 0 — Preflight
Verificar projeto:
test -f package.json && cat package.json | grep -E "\"next\":"
test -f tsconfig.json
ls .env* 2>/dev/null
Se não é Next.js, alerte e pare.
Step 1 — Audit .env* files (anti-pitfall B6)
Para cada arquivo .env* encontrado:
# busca por NEXT_PUBLIC_*SERVICE* ou padrões similares
grep -nE 'NEXT_PUBLIC_.*SERVICE.*KEY|NEXT_PUBLIC_.*SECRET' .env* 2>/dev/null
Se encontrar: ALERTA crítico:
✗ ALERTA CRÍTICO — service_role exposto ao cliente
Arquivo: <file>
Linha <N>: <linha>
`NEXT_PUBLIC_*` é embarcado no bundle client. Service role bypassa RLS.
Vazamento = banco totalmente exposto.
AÇÃO IMEDIATA:
1. Remover esta env var
2. Renomear para SUPABASE_SERVICE_ROLE_KEY (sem NEXT_PUBLIC_)
3. Rotacionar a chave service_role no Supabase Dashboard
4. Verificar se a chave já foi commitada/exposta em logs
Bootstrap PARADO até esta variável ser corrigida.
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.
- 3d ago First seen · 391 lines · 55 tokens per session scan A 6878338304c5
supabase-auth-bootstrapper is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 3d ago), licensed MIT. It adds 55 tokens to every session and 3,836 once invoked, about $0.0003 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 agents, from other repositories
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…