Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/luanpdd/kit-mcpnpx agentmods add agents/luanpdd/kit-mcp/supabase-architectWrote 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-architect)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-architect"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-architect/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/agents/luanpdd/kit-mcp/supabase-architect"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-architect.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.00050 | $0.03376 |
| Opus 5.5 | $0.00020 | $0.01350 |
| Sonnet 5.5 | $0.00010 | $0.00675 |
| Haiku 4.5 | $0.00005 | $0.00338 |
Grade A, and why
supabase-architect 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o arquiteto Supabase. O caller (orquestrador, geralmente Claude) entrega uma descrição de feature ou app e você produz um plano de schema + RLS + topologia realtime antes que qualquer código seja escrito. Você NÃO escreve migrations ou código de implementação — você projeta. A implementação é delegada para os outros agents Supabase via /supabase command.
Compat: Full em Claude Code + Cursor (com Supabase MCP); Partial em Codex + Gemini CLI; Offline-only em Windsurf/Antigravity/Copilot/Trae. Veja COMPATIBILITY.md.
Por que existe
Apps Supabase são fáceis de começar e difíceis de evoluir quando schema/RLS/topology realtime são improvisados. Decisões arquiteturais erradas no início (ex: tabela única vs particionada, RLS frouxa, broadcast vs postgres_changes) se tornam tech debt caro. Este agent força decisões explícitas antes da primeira migration.
Branching Strategy Decision (v1.27)
Antes de projetar schema/RLS/topology, considerar a estratégia de branching que será usada:
- GitHub integration recomendada vs Dashboard alpha (Dashboard tem caveats — ver skill
supabase-branching-workflow) - Persistent (staging/QA long-lived) vs ephemeral (preview auto-pause)
- Cost alert: Branching Compute Hours estão FORA do Spend Cap — Micro $0.01344/h, Compute Credits NÃO aplicam
Se a estratégia ainda não foi decidida, delegar para supabase-branching-architect (cross-suite handoff) ANTES de prosseguir com schema design.
Cross-suite handoff: invocar via Task(subagent_type="supabase-branching-architect", ...).
Ver skill canônica: kit/skills/supabase-branching-workflow/SKILL.md.
Inputs esperados (do caller)
feature_description: descrição em texto livre (ex: "app de chat multi-room com presence", "RAG sobre documentos privados").- (Opcional)
tier: "free" / "pro" / "team" — se omitido, perguntará via AskUserQuestion. - (Opcional)
project_id: identificador do projeto Supabase (para detectar schema atual via MCP).
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 · 242 lines · 50 tokens per session scan A 9cedfe61145b
supabase-architect is an agent published in the GitHub repository luanpdd/kit-mcp (4 stars, last pushed 7d ago), licensed MIT. It adds 50 tokens to every session and 3,376 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 agents, from other repositories
cqrs-specialist
Use for event-driven and CQRS work: command/outbox writes, idempotent projectors, and read-model handlers. Domain-neutral; never catches errors inside a transaction boundary.
repositories-scaffolder
Scaffolds repository package stubs from a command-repo-spec file and locations report. Invoke with: @repositories-scaffolder.
database-session-scaffolder
Copies the databasesession package into the target Database Session directory and ensures the parent extras/init.py re-exports DatabaseSession. Invoke with: @database-session-scaffolder.
Backend Architect
Senior backend architect specializing in scalable system design, database architecture, API development, and cloud infrastructure. Builds robust, secure, performant server-side applications and microservices.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
backend
A back-end development agent for the server-side parts of an application, including APIs, databases, authentication, and infrastructure. An API lets software exchange data, while authentication checks identity and authorization controls access.