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.
npx skills add Phaedra-Solutions/cursor-rules --skill upgrade-supabasegit clone --depth 1 https://github.com/Phaedra-Solutions/cursor-rulesWrote 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.
[](https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-supabase)<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-supabase"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-supabase/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.
<a href="https://agentmods.dev/skills/phaedra-solutions/cursor-rules/upgrade-supabase"><img src="https://agentmods.dev/badge/skills/phaedra-solutions/cursor-rules/upgrade-supabase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00121 | $0.02408 |
| Opus 5.5 | $0.00048 | $0.00963 |
| Sonnet 5.5 | $0.00024 | $0.00482 |
| Haiku 4.5 | $0.00012 | $0.00241 |
Grade A, and why
upgrade-supabase 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Supabase
When to use
- The project uses the legacy
anon/service_rolekeys (deprecated by the end of 2026),import_map.jsonor URL imports in Edge Functions. - The user asks to harden a Supabase project or clear Security Advisor findings.
Parts A, B and C are independent. Do them in that order unless the user picks one; each ends with Verify.
Before you start
- Read the CLI version and the
supabase-js,@supabase/ssrand@supabase/serverversions; list every client of the project: web apps, mobile apps (and which builds are still in use), servers, workers, CI jobs, Edge Functions, Database Webhooks,pg_net/cron jobs, and third-party integrations. - The working tree must be clean; work on a branch. Never apply anything to production from this session.
- Ask the user:
- which environments exist (local, preview branches, staging, production) and the order to migrate them (always staging first);
- who can create and deactivate keys in the Dashboard (Owner or Administrator) and who sets production secrets;
- whether old mobile builds must keep working (they hold the anon key until users update);
- whether network installs are approved (
core/supply-chaincooldown applies to newnpm:versions).
- Never print, log or paste key values into chat, commits or files. Refer to them by variable name.
Steps
Part A: publishable and secret keys
-
Inventory. List every place each legacy key is used, with file and line:
git grep -nE "SUPABASE_ANON_KEY|SUPABASE_SERVICE_ROLE_KEY|ANON_KEY|SERVICE_ROLE|service_role" -- ':!*.md' git grep -nE "net\.http_post|Authorization.*Bearer" -- 'supabase/**/*.sql'Also ask about Dashboard-configured Database Webhooks and cron jobs, which aren't in the repo. If a
service_rolekey appears in client code, stop and tell the user to treat it as leaked (secrets-scanskill). -
Create keys. The user creates publishable and secret keys in Dashboard → Settings → API Keys. Legacy keys keep working alongside. Suggest one named secret key per backend service (
default,billing,worker) so each rotates alone. -
Clients (publishable key). Replace the anon key with the publishable key in browser, mobile, desktop and CLI config (
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEYor the project's naming). RLS behaves the same. Ship mobile releases early; old builds keep working until the legacy keys are deactivated. -
Servers (secret key). Replace the service-role key with a secret key in server-only env vars and the secret manager. Confirm the admin client lives in a server-only module. Secret keys return 401 when sent from a browser.
-
Edge Functions.
- Read keys from
SUPABASE_SECRET_KEYS/SUPABASE_PUBLISHABLE_KEYS(JSON objects keyed by name):
- Read keys from
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.
- 3d ago First seen · 130 lines · 121 tokens per session scan A a58e2302c642
upgrade-supabase is a skill published in the GitHub repository Phaedra-Solutions/cursor-rules (4 stars, last pushed 2d ago), licensed MIT. It adds 121 tokens to every session and 2,408 once invoked, about $0.0005 per session on Opus 5.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-11-01.
Other skills, from other repositories
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.
nextjs-fullstack
Use for Next.js App Router, React Server Components, server actions, API routes, auth, database integration, caching, deployment, or full-stack product features.
flask
Skill "flask" from rishapgandhi/python-skills, covering flask skill, stack, project structure, app factory and app/init.py.
django
Skill "django" from rishapgandhi/python-skills, covering django skill, stack, project structure, settings pattern (split by environment) and config/settings/base.py.
drf
Skill "drf" from rishapgandhi/python-skills, covering django rest framework (drf) skill, stack additions (on top of django), settings, config/settings/base.py and serializer standards.
fastapi
Skill "fastapi" from rishapgandhi/python-skills, covering fastapi skill, stack, project structure (fastapi-specific additions), app factory pattern and app/main.py.