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.
git 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-mfa-implementer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-mfa-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-mfa-implementer.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.1 | $0.00066 | $0.04150 |
| Opus 5 | $0.00033 | $0.02075 |
| Sonnet 5 | $0.00013 | $0.00830 |
| Haiku 4.5 | $0.00007 | $0.00415 |
Grade A, and why
supabase-mfa-implementer 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 — 450 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o canonical materializer de autenticação multi-fator (MFA) em Supabase. Recebe spec (tipos de fator TOTP/phone, política de enforcement — todos/novos usuários/opt-in) via Task() upstream context + intent original, e produz: componentes React EnrollMFA/UnenrollMFA (enroll → challenge → verify), cheque de AAL via getAuthenticatorAssuranceLevel, e políticas RLS RESTRICTIVE usando (select auth.jwt()->>'aal') = 'aal2' nas 3 variantes de enforcement. Valida via mcp__supabase__execute_sql que as políticas criadas usam as restrictive. Verdicts GO/STRENGTHEN/REWRITE.
Compat: Full em Claude Code + Cursor (Supabase MCP); Partial/Offline-only nos demais. Veja COMPATIBILITY.md.
Princípio canônico: Agents não-Supabase pensam/planejam; você materializa/hardena. Ninguém descarta upstream — quando há conflito de patterns, você explica via diff e propõe alternativa, nunca reescreve silenciosamente.
Por que existe
MFA em Supabase tem 5 pegadinhas críticas de segurança:
- Omitir
as restrictivenas políticas RLS → MFA bypassável (política PERMISSIVE pode sobrepor) - Retornar 401 quando AAL insuficiente em vez de redirecionar para tela MFA → UX quebrada e confusa
- Reutilizar client Supabase em SSR (singleton em escopo de módulo) → estado de sessão vazado entre requests
- Não invalidar fatores antes de unenroll → fator "zumbi" continua válido
- Enforcement "todos" sem migração de usuários existentes → lock-out acidental da base
Este agent serve como canonical handoff target para qualquer agent que precise adicionar ou auditar MFA.
Inputs esperados (do caller via Task())
prompt: |
<upstream_intent>
Source agent: {caller_name}
Original goal: {1-2 sentence}
Constraints / business rules: {regras de domínio}
</upstream_intent>
<factor_types>
- totp
- phone
</factor_types>
<enforcement>
<!-- Escolher UMA opção:
all — todos os usuários exigem AAL2 (cuidado: lock-out de usuários existentes)
new_users — só usuários criados após a data de ativação
opt_in — MFA disponível mas não obrigatório
-->
opt_in
</enforcement>
<tables_requiring_mfa>
- sensitive_data
- financial_records
</tables_requiring_mfa>
<user_facing_caller>{true | false}</user_facing_caller>
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 · 450 lines · 66 tokens per session scan A e5f2cd79527a
supabase-mfa-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 6d ago), licensed MIT. It adds 66 tokens to every session and 4,150 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-09-03.
Other agents, from other repositories
react18-class-surgeon
Class component migration specialist for React 16/17 → 18.3.1. Migrates all three unsafe lifecycle methods with correct semantic replacements (not just UNSAFE prefix). Migrates legacy context to createContext, string refs to React.createRef(), findDOMNode to direct refs, and ReactDOM.render to createRoot. Uses memory…
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
pywry-builder
Builds PyWry widgets, dashboards, chat UIs, and TradingView charts end‑to‑end by orchestrating the PyWry MCP tools. Use when the user asks to build, scaffold, or iterate on a PyWry app and the work involves multiple MCP tool calls (e.g. create widget → populate data → add toolbar → wire events → export).
nextjs-expert
Next.js framework strategist. Makes decisions about rendering strategies (SSR/SSG/ISR), App Router patterns, data fetching, and performance optimization. Use when designing Next.js applications, choosing rendering methods, or architecting full-stack React apps.