supabase-social-auth-implementer

supabase-social-auth-implementer is an agent for Claude Code from luanpdd/kit-mcp. It costs 54 tokens per session (3,982 once invoked), scanned A, original, MIT.

A Supabase assistant for adding social sign-in through OAuth, the standard process that lets users log in with services such as Google, Apple, or GitHub. It supports browser and native-app login flows.

In plain words
What is it for?
It prepares provider configuration, OAuth login code, the PKCE callback route, token exchange logic, and native sign-in components.
Why use it?
It helps prevent broken redirects, exposed tokens, and incomplete PKCE callback handling during third-party login.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit It prepares provider configuration, OAuth login code, the PKCE callback route, token exchange logic, and native sign-in components.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/luanpdd/kit-mcp/supabase-social-auth-implementer
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.

Clone the repo
git clone --depth 1 https://github.com/luanpdd/kit-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for supabase-social-auth-implementer

README.md
[![agentmods](https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-social-auth-implementer.svg)](https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-social-auth-implementer)
Your own site
<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-social-auth-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-social-auth-implementer.svg" alt="Measured on agentmods" height="20"></a>
Per session 54 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,982 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00054 $0.03982
Opus 5 $0.00027 $0.01991
Sonnet 5 $0.00011 $0.00796
Haiku 4.5 $0.00005 $0.00398

Measured 3d ago against content hash dc0b826d1380, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

supabase-social-auth-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.

kit/agents/supabase-social-auth-implementer.md · 453 lines

How it starts

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

Você é o canonical materializer de social login / OAuth em Supabase. Recebe spec (providers desejados — google/github/apple/facebook/linkedin/custom, framework, web vs native) via Task() upstream context + intent original, e produz: checklist de configuração do provider (callback URL canônica), código signInWithOAuth/signInWithIdToken, rota callback PKCE /auth/callback com exchangeCodeForSession, e componentes de native sign-in (Google One Tap, Apple Sign-In). Verdicts construtivos GO/STRENGTHEN/REWRITE alinhados com supabase-auth-bootstrapper.

Compat: Full em todos os IDEs (filesystem-only). 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

Social OAuth em Supabase tem 6 pegadinhas que LLMs erram sistematicamente:

  1. Usar implicit flow no servidor (JWT exposto na URL) em vez de PKCE
  2. Faltar rota callback PKCE — fluxo quebra silenciosamente após redirect do provider
  3. redirectTo fora da allowlist do Supabase Dashboard → erro redirect_uri_mismatch
  4. Apple Sign-In: não salvar user.name no primeiro sign-in (Apple não reenvia)
  5. Google refresh token: esquecer access_type: offline → não obtém refresh token
  6. Native: misturar signInWithOAuth (abre browser) com signInWithIdToken (token nativo)

Este agent serve como canonical handoff target para agents externos que precisam materializar autenticação social segura.

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>

  <providers>
  - google
  - github
  - apple
  - facebook
  - linkedin_oidc
  </providers>

  <framework>{nextjs | sveltekit | nuxt | expo | react-native}</framework>
  <platform>{web | native | both}</platform>
  <redirect_base_url>https://app.example.com</redirect_base_url>
  <user_facing_caller>{true | false}</user_facing_caller>

Read the full file on GitHub · 453 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. 3d ago First seen · 453 lines · 54 tokens per session scan A dc0b826d1380

Subscribe to this mod's changes

supabase-social-auth-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 54 tokens to every session and 3,982 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.

Related

Other agents, from other repositories

Power Platform MCP Integration Expert

Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.

github/awesome-copilot · 31 tokens

php-developer

Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.

davepoon/buildwithclaude · 51 tokens

backend-reviewer

Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

dotnet-architecture-reviewer

Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…

StefanTheCode/dotnet-ai-toolkit · 102 tokens