Supabase Key Exposure Check (Free, Offline)
Free offline check that finds Supabase service_role / sb_secret_ keys leaking into browser code, public env vars, bundles or committed files.
Free
Works with the AI Agents you already use
About this skill
Use before launching a Supabase app, or when you suspect a key leaked. Scans a repo or build folder (dist, .next, build), decodes legacy JWT keys offline to read the role claim (anon vs service_role), recognises sb_publishable_ and sb_secret_ keys, and returns a PASS/FAIL verdict with file:line evidence and redacted values.\n\nFlags a secret key that reaches: a public-prefixed env var (NEXT_PUBLIC_, VITE_, EXPO_PUBLIC_), a browser bundle, a use-client file, or a committed env file. Tells you to rotate and how.\n\nFree, offline, read-only. Standard-library Python 3.8+, no network, no account. Never prints a full key. A PASS covers these patterns only and is not a full secret scan; git history is not searched.\n\nThe anon key is public by design, so RLS is your only wall: the paid Supabase RLS Launch Gate checks that next.
How to use
- 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
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
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
2 uses
Times used to date
Free forever
No account required to browse
Trust & safety
Security scan
Security scan passed 1 month ago
- Free with an Agensi account
Requires