More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Supabase Config and Functions Check

    1

    This skill finds those and the other Supabase mistakes below before you deploy, and tells you how to fix each one.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Supabase Config and Functions Check

    Supabase Config and Functions Check

    Example session with this skill installed

    Check this project with supabase-config-functions-check.

    • Read your context and instructions
    • Compiled the supabase config

    $ python3 scripts/check_supabase_config.py examples/risky
    BLOCK supabase/config.toml:16 U04 REDIRECT_ALLOWS_ANY_SITE
    "https://.vercel.app/**",
    Why: site_url or additional_redirect_urls has a wildcard that matches sites other people can own: ** in the host, a host that is only , a * in the registered domain (.com, acme
    .com), or a label of only wildcards under a shared hosting domain (.vercel.app, -.vercel.app, .netlify.app, .pages.dev). Supabase Auth then sends magic-link, OAuth and password-reset redirects, with their codes or tokens, to a site an attacker controls, who can sign in as that user. This includes the Netlify preview pattern the Supabase docs show (https://--your-site.netlify.app/): its ** also matches a path on any other domain that ends in --your-site.netlify.app/. App deep links (myapp://, com.example.app://) are not web sites and are not reported.
    Safer: List exact URLs for production (https://app.example.com/auth/callback). For preview deployments limit the wildcard to your own team or domain, as the Supabase docs show for Vercel (https://
    -your-team.vercel.app/**), use a single * instead of ** before the Netlify suffix (https://
    --your-site.netlify.app/**), or use a subdomain of a domain you own (https://
    .example.com/**).

    BLOCK supabase/config.toml:33 U03 SECRET_IN_CONFIG_TOML
    BLOCK web/.env.example:4 U01 SERVICE_KEY_EXPOSED_TO_BROWSER
    BLOCK web/scripts/seed-admin.ts:5 U02 SERVICE_KEY_IN_FILE
    REVIEW supabase/config.toml:17 U16 PLAIN_HTTP_REDIRECT_URL
    REVIEW supabase/config.toml:19 U15 AUTH_SAFEGUARD_WEAKENED
    REVIEW supabase/config.toml:22 U14 ANONYMOUS_SIGN_INS_WITHOUT_CAPTCHA
    REVIEW supabase/config.toml:23 U13 SHORT_MINIMUM_PASSWORD
    REVIEW supabase/config.toml:28 U12 SIGNUP_WITHOUT_EMAIL_CONFIRMATION
    REVIEW supabase/config.toml:36 U17 PUBLIC_STORAGE_BUCKET
    REVIEW supabase/functions/stripe-webhook/index.ts:10 U11 OPEN_FUNCTION_USES_SERVICE_KEY
    REVIEW web/middleware.ts:18 U18 GETSESSION_TRUSTED_ON_SERVER

    (Each finding also has Why and Safer lines, as in the first one.)
    Verdict: BLOCK. Checked 5 files, 5 with Supabase content.
    This is a static check of file text. NOT FLAGGED is not a guarantee.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    NEXT_PUBLIC_SUPABASE_SERVICE_ROLE_KEY ships the key that bypasses every Row Level Security policy to every visitor, and "https://*.vercel.app/**" in your redirect list lets anyone with a Vercel account receive your users' magic-link and OAuth redirects. This skill finds those and the other Supabase mistakes below before you deploy, and tells you how to fix each one.

    Your agent runs a scanner on supabase/config.toml (including [remotes] branch blocks), Edge Function code in supabase/functions, JavaScript and TypeScript client and server code (Next.js, SvelteKit, Nuxt, Vite, Astro, Expo), Expo app.json and eas.json, Python, Dart, Swift and Kotlin files that hold keys, and .env files. It reads the role inside legacy JWT keys, knows the new sb_publishable_ and sb_secret_ formats, ignores the fixed public keys of the local CLI stack, leaves app deep links (myapp://**) alone, treats env() and encrypted: values as references, and judges sign-up and password settings only when config.toml sets up a deployed project, so the file supabase init writes is not flagged. It never runs code or connects to Supabase. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.

    What it checks

    BLOCK

    • U01: the service_role or secret key in a public variable (NEXT_PUBLIC_, VITE_, EXPO_PUBLIC_, PUBLIC_ and others, also in eas.json), a public variable holding a service key, or a service key under Nuxt runtimeConfig.public, Expo extra (app.config or app.json), Next.js env or Vite define
    • U02: a service_role JWT or sb_secret_ key written in code, app.json, eas.json or a committed env template
    • U03: OAuth, SMTP, SMS, CAPTCHA, auth hook, Studio, S3, Edge Runtime or Vault secrets written in config.toml instead of env()
    • U04: redirect URLs whose wildcards accept other people's sites (** in the host, including the Netlify preview pattern from the docs, *.com, *.vercel.app, -.vercel.app, *.netlify.app, *.pages.dev and other shared hosts)

    REVIEW

    • U11: Edge Functions with JWT verification off (verify_jwt = false, --no-verify-jwt, withSupabase auth 'none' or 'publishable') that use the service key and never check the caller (user JWT, secret key, webhook signature or secret header)
    • U12: email sign-up without email confirmation on a deployed project
    • U13: a minimum password length below 8 on a deployed project
    • U14: anonymous sign-ins without CAPTCHA on a deployed project
    • U15: JWT expiry above one hour, refresh token rotation off, single-address email change confirmation, or the nonce check skipped on a deployed project
    • U16: site or redirect URLs with plain http:// for hosts that are not local
    • U17: public storage buckets, in config.toml or created in code, unless the name's words mark public content such as avatars or profile-pictures
    • U18: getSession() trusted in server code (middleware, proxy, route handlers, server components and actions) without getClaims() or getUser()

    What's included

    • The scanner (Python 3.9+, standard library only)
    • A rules guide with the reason, safer approach and official Supabase source for each rule
    • A risky and a safe example project (config.toml, an Edge Function, a Next.js middleware, a seed script and an env template), and the real report the scanner produces on the risky one

    Limits It reads files as written: settings changed only in the Supabase dashboard, Row Level Security policies and SQL migrations, and secrets set with supabase secrets set are not known. An Edge Function's caller check is looked for in the same file, and U11 needs the project folder that holds config.toml or the deploy script. Browser exposure is judged by variable prefixes and the Nuxt, Expo, Next.js env and Vite define settings, not by tracing imports. NOT FLAGGED is not a guarantee.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    Static check of config and code text. Dashboard-only settings, RLS policies, SQL migrations and secrets stored with supabase secrets set are not known, and imports are not traced. NOT FLAGGED is not a guarantee.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 4 days ago

    Software
    tsxNode.jsPython

    Permissions

    Terminal / Shell
    Read Files

    Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert secrets (not-a-real-...) for the scanner to find. Nothing in it is run.

    Listed4 days ago

    What's inside

    Frequently Asked Questions

    No. The script reads local files only and makes no network calls.

    No. It only reports. Your agent changes files only if you ask it to.

    Any agent that supports SKILL.md skills and can run a terminal command, such as Claude Code. It needs Python 3.9 or newer and nothing else.

    No. It reads supabase/config.toml, edge functions and your app code as text. It never calls Supabase, runs the CLI or uses a key, and keys it finds are masked.

    BLOCK: fix it before you ship. REVIEW: check it before release. NOT FLAGGED: no rule matched. It is a static check, so NOT FLAGGED is not a guarantee.

    New in Security