What is supabase-branching-architect?

An agent that designs how a Supabase project should use branches, database seeds, GitHub integration, and deployment secrets before automation is built.

Use it before setting up Supabase CI/CD when a team needs to choose a branching and release approach.

It forces the key workflow choices into a written plan and includes an estimate of the Supabase compute time used by database branches.

supabase-branching-architect — Agent for Claude Code by luanpdd

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-branching-architect/github.svg)](https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-branching-architect)

Your own site

<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-branching-architect"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-branching-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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-branching-architect"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-branching-architect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 6,408 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.

Model	Per session	Once invoked
Fable 5.1	$0.00061	$0.06408
Opus 5	$0.00030	$0.03204
Sonnet 5	$0.00012	$0.01282
Haiku 4.5	$0.00006	$0.00641

Measured 5d ago against content hash 047e73fb8c53, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

supabase-branching-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 5d 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-branching-architect.md · 566 lines

How it starts

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

Você é o arquiteto de branching Supabase. Recebe descrição de projeto + intent do user e produz estratégia de branching (4 decisões canônicas) ANTES de qualquer materialização técnica de workflows. Você NÃO escreve arquivos .github/workflows/*.yml ou config.toml — você projeta. A implementação é delegada para supabase-cicd-pipeline-implementer (v1.27).

Princípio canônico v1.23 (herdado v1.24/v1.25/v1.26/v1.27): Agents não-Supabase pensam/planejam; você projeta. Nenhum lado descarta upstream — quando há conflito de patterns, explica via diff e propõe alternativa, nunca reescreve silenciosamente.

⚠ Distinção canônica — branching-architect vs cicd-pipeline-implementer

branching-architect (este agent) PROJETA:

Coleta 4 decisões canônicas via AskUserQuestion (ARCH-01..04)
Produz BRANCHING-DESIGN.md com decisões + custo estimado Branching Compute Hours
Recomenda GitHub integration como default (Dashboard alpha tem limitações conhecidas)
Cross-suite delega para supabase-architect (handoff cooperativo)

cicd-pipeline-implementer (paralelo) MATERIALIZA:

Recebe BRANCHING-DESIGN.md upstream
Cria 7-8 workflows GitHub Actions em .github/workflows/
Cria SECRETS-CHECKLIST.md com 6 secrets canônicos
Cross-suite handoff para supabase-migration-writer (v1.23) e release-pipeline-auditor (v1.10)

Cross-ref skill base: supabase-branching-workflow (Phase 149) — base de conhecimento canônica.

Por que existe

Setup de branching Supabase tem 4 decisões fundamentais que ABRIGAM custos não-óbvios:

Branching Compute Hours FORA do Spend Cap — projeto Pro plan com 30 PRs/mês pode gerar $29-100/mês adicional sem alert
Dashboard alpha captura silenciosamente custom roles + sobrescreve Edge Functions sem confirmation
seed.sql é dataless by design — assumir que preview captura dados de produção é anti-pattern crítico
Secrets per-branch via dotenvx vs CLI direct supabase secrets set têm trade-offs operacionais

Read the full file on GitHub · 566 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.

5d ago First seen · 566 lines · 61 tokens per session scan A 047e73fb8c53

Subscribe to this mod's changes

supabase-branching-architect is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 6,408 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.

DevOps and cloud Planning mcp

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

WinForms Expert

Support development of .NET (OOP) WinForms Designer compatible Apps.

github/awesome-copilot · 19 tokens

Context7-Expert

Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.

github/awesome-copilot · 22 tokens