What is supabase-cicd-pipeline-implementer?

An agent that creates GitHub Actions workflows for Supabase continuous integration and delivery (CI/CD), meaning automated checks and deployments, plus a checklist of required secrets.

Use it to set up automated Supabase checks and deployments after deciding how branches, seeds, GitHub integration, and secrets should work.

It turns a chosen Supabase branching plan into repeatable automation and makes the credentials needed by the workflows explicit.

supabase-cicd-pipeline-implementer — 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-cicd-pipeline-implementer.svg)](https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-cicd-pipeline-implementer)

Your own site

<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-cicd-pipeline-implementer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-cicd-pipeline-implementer.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 8,133 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.00066	$0.08133
Opus 5	$0.00033	$0.04066
Sonnet 5	$0.00013	$0.01627
Haiku 4.5	$0.00007	$0.00813

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

Security

Grade A, and why

supabase-cicd-pipeline-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 4d 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-cicd-pipeline-implementer.md · 778 lines

How it starts

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

Você é o canonical materializer pipeline CI/CD Supabase. Recebe BRANCHING-DESIGN.md de supabase-branching-architect (v1.27) ou user direto, e materializa 7-8 workflows GitHub Actions canônicos em .github/workflows/ + SECRETS-CHECKLIST.md com 6 secrets canônicos. Cross-suite handoff para supabase-migration-writer (v1.23) e release-pipeline-auditor (v1.10). Verdicts GO/STRENGTHEN/REWRITE-com-confirmação alinhados com princípio canônico v1.23.

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

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

branching-architect (Phase 154 paralelo) PROJETA:

Coleta 4 decisões canônicas via AskUserQuestion (ARCH-01..04)
Produz BRANCHING-DESIGN.md (decisões + custo estimado)
Cross-suite delega para supabase-architect

cicd-pipeline-implementer (este agent) MATERIALIZA:

Recebe BRANCHING-DESIGN.md como input 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) — se workflows referenciam novas migrations
Cross-suite handoff para release-pipeline-auditor (v1.10) — audit hermeticidade do pipeline gerado

Cross-ref skill base: supabase-ci-cd-github-actions (Phase 151) — base de conhecimento canônica com 8 workflows YAML completos.

Por que existe

CI/CD Supabase via GitHub Actions tem 8 workflows canônicos da doc oficial, cada um com seus caveats específicos. Esquecer qualquer um quebra silenciosamente:

Esquecer concurrency em production.yml → race condition em schema_migrations quando 2 PRs mergem em sequência rápida
Esquecer WARNING "never backup to public repo" no backup.yml → time torna repo público posteriormente sem auditoria → vazamento de PII permanente
Esquecer paths: ['supabase/**'] em notify-failure.yaml → check ausente em PRs frontend-only → branch protection bloqueia merge incorretamente
Esquecer required check enforcement → workflows rodam mas merge passa sem ✓ verde (defaults soft)
Esquecer rotação de SUPABASE_DB_PASSWORD → workflows quebram silenciosamente após 90 dias se time roda rotação no Dashboard sem update no secret GitHub

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

4d ago First seen · 778 lines · 66 tokens per session scan A 61e0cf5fcac8

Subscribe to this mod's changes

supabase-cicd-pipeline-implementer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed today), licensed MIT. It adds 66 tokens to every session and 8,133 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.

CI and CD DevOps and cloud Git and workflow mcp

aidlc-pipeline-deploy-agent

CI/CD engineer and release manager responsible for pipeline configuration, deployment strategy, and release execution. Leads Practices Discovery, CI Pipeline, Deployment Pipeline, and Deployment Execution stages.

awslabs/aidlc-workflows · 41 tokens

bt6-release-integrator

Runs conservative one-at-a-time merge trains for BT6 repositories with CI, evidence, compatibility, and issue reconciliation gates.

elder-plinius/T3MP3ST · 30 tokens

pr-manager

Create/update PR/MR title and description.

juliusz-cwiakalski/agentic-delivery-os · 12 tokens

gitops-ci-specialist

Use this agent when you need to commit code to GitHub and want to ensure CI/CD pipeline success. Examples: Context: User has written new code and wants to commit it safely. user: 'I've added a new authentication module. Can you help me commit this properly?' assistant: 'I'll use the gitops-ci-specialist agent to…

niksacdev/engineering-team-agents · 210 tokens

platform-engineer

Platform and forge specialist — CI/CD, GitHub/GitLab PR lifecycle, merge-conflicts, worktrees, integrations (Slack/Linear/ClickUp/MCP), loops/swarm, triage, llm-cost-advisor, cli-for-agents, herdr. Use when: CI failure, PR/MR lifecycle, worktrees, MCP setup, incidents, integrations, swarm/loops, CLI ergonomics.

ulises-jeremias/agent-toolkit · 88 tokens

committer

Create one Conventional Commit.

juliusz-cwiakalski/agentic-delivery-os · 8 tokens