Supabase Local Development

A local development setup for Supabase, a backend platform built around PostgreSQL databases. It runs the database and Supabase services—such as login, file storage, server functions, and realtime updates—in Docker on your computer.

In plain words
What is it for?
Use it to initialize a Supabase project, start local PostgreSQL and services, manage migrations, configure environment variables, and generate TypeScript database types.
Why use it?
It lets you develop without depending on a remote database and test database changes safely before deploying them.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/constellos/claude-code/supabase-local-dev
Any agent
npx skills add constellos/claude-code --skill supabase-local-dev
Clone the repo
git clone --depth 1 https://github.com/constellos/claude-code

Made for: Claude Code, Codex.

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,613 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
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 $0.00080 $0.01613
Opus 5 $0.00040 $0.00807
Sonnet 5 $0.00016 $0.00323
Haiku 4.5 $0.00008 $0.00161

Measured 2d ago against content hash a09e083cfbf9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

Supabase Local Development scanned grade B with 1 finding 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 2d 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo systemctl start docker
plugins/nextjs-supabase-ai-sdk-dev/skills/supabase-local-dev/SKILL.md · 264 lines

How it starts

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

Supabase Local Development

Overview

Supabase Local Development provides a complete local Postgres database with all Supabase services (Auth, Storage, Edge Functions, Realtime) running in Docker containers. This enables offline development, faster iteration, and safe database migrations before deploying to production.

Key benefits:

  • Full Supabase stack running locally
  • Faster development without network latency
  • Safe migration testing before production
  • Automatic TypeScript type generation
  • Environment variable management

Skill-scoped Context

Official Documentation:

Prerequisites

Docker Runtime

Supabase local development requires a Docker-compatible container runtime:

  • Docker Desktop (macOS, Windows, Linux)
  • Rancher Desktop (macOS, Windows, Linux)
  • OrbStack (macOS) - Recommended for Apple Silicon
  • Podman (macOS, Windows, Linux)

Verify Docker is running:

docker info

Supabase CLI

Install via npm (recommended for Next.js projects):

npm install -g supabase

Or via Homebrew (macOS):

brew install supabase/tap/supabase

Verify installation:

supabase --version

Workflow

Step 1: Initialize Supabase Project

supabase init

This creates a supabase/ directory with:

  • config.toml - Local configuration
  • seed.sql - Optional seed data
  • migrations/ - Database migrations

Step 2: Start Local Services

supabase start

Read the full file on GitHub · 264 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. 2d ago First seen · 264 lines · 80 tokens per session scan B a09e083cfbf9

Subscribe to this mod's changes

Supabase Local Development is a skill published in the GitHub repository constellos/claude-code (5 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 1,613 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens