Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/magnus919/agent-skillsnpx agentmods add skills/magnus919/agent-skills/supabaseWrote 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/magnus919/agent-skills/supabase)<a href="https://agentmods.dev/skills/magnus919/agent-skills/supabase"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/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/magnus919/agent-skills/supabase"><img src="https://agentmods.dev/badge/skills/magnus919/agent-skills/supabase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 19 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00094 | $0.01795 |
| Opus 5 | $0.00047 | $0.00898 |
| Sonnet 5 | $0.00019 | $0.00359 |
| Haiku 4.5 | $0.00009 | $0.00179 |
Grade A, and why
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 6d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase
Treat Supabase as a Postgres-centered system with multiple independently versioned services, not as one opaque backend. The managed platform, CLI local stack, and official self-hosted Compose stack share concepts but are different operating environments. Identify which one the task targets before choosing commands.
Operating contract
- Discover the target and current state before changing it: managed project, CLI local stack, or self-hosted Compose; CLI and service versions; project link; database and migration state; enabled services; public URLs; backup and rollback path.
- Confirm target, scope, and rollback path before the first mutation. Read-only discovery may proceed without confirmation. An explicit user directive to deploy or change the named target satisfies this gate.
- Keep publishable keys client-side and secret/service-role keys server-side only. Never print, commit, or place secret keys, database passwords, JWT signing material, SMTP credentials, or connection strings containing passwords in reports.
- Make database changes through versioned migrations. Review generated diffs as drafts, replay the full chain, test RLS negative cases, and regenerate client types before deployment.
- For self-hosting, use the official
supabase/supabaseDocker directory and itssetup.sh,run.sh, update notes, and tests. Do not invent a reduced Compose stack unless the user explicitly wants one and accepts the lost capabilities. - Verify at the delivery boundary: container health is not API health; an API response is not authorization proof; a backup is not recovery evidence.
Choose the path
| Need | Read first |
|---|---|
| Understand services, trust boundaries, keys, and environment differences | architecture and boundaries |
| Install/use the CLI, establish a local workflow, or operate managed Functions, secrets, branches, SSL enforcement, CIDR restrictions, and network bans | local development and CLI |
| Create schemas, migrations, seed data, RLS policies, tests, and generated types | database development and testing |
| Build with Auth, REST, Realtime, Storage, and Edge Functions | application services |
| Deploy or harden the official Docker stack | self-hosting deployment |
| Back up, restore, update, upgrade, monitor, or recover a self-hosted instance | administration and recovery |
| Diagnose unhealthy containers, bad URLs, auth failures, drift, or migration failures | troubleshooting |
| Evaluate how well an agent can use Supabase with scored scenarios | agent evals harness |
| Check claim currency or authoritative source coverage | source index |
What ships with it
11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- evals/evals.json 9.9 KB
- README.md 3.4 KB
- references/administration-and-recovery.md 7.3 KB
- references/agent-evals.md 8.3 KB
- references/application-services.md 5.1 KB
- references/architecture-and-boundaries.md 5.4 KB
- references/database-development-and-testing.md 7.5 KB
- references/local-development-and-cli.md 7.6 KB
- references/self-hosting-deployment.md 6.5 KB
- references/source-index.md 4.2 KB
- references/troubleshooting.md 6.5 KB
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.
- 6d ago First seen · 123 lines · 94 tokens per session scan A 52fc86c1c8fb
supabase is a skill published in the GitHub repository magnus919/agent-skills (75 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,795 once invoked, about $0.0005 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.
Other skills, from other repositories
ag-referencia-supabase
Patterns para Supabase, PostgreSQL, RLS, migrations, e Zod schemas.
supabase
Supabase provides Postgres database access, authentication, edge functions, and storage. This skill covers the @supabase/supabase-js client and Row Level Security (RLS).
stack-supabase
Supabase platform knowledge overlay for the ETYB team. Loads when work involves the Supabase ecosystem — Postgres (Supabase-hosted), Row-Level Security (RLS), Supabase Auth, Storage, Realtime, Edge Functions, Database Webhooks, Database Functions, Supavisor pooler, pgvector, pgcron, pgnet, pggraphql, pgjsonschema…
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
sqlmodel-database
Design and implement database schemas using SQLModel with sync and async patterns. Use this skill when creating database models, setting up Neon PostgreSQL connections, defining relationships (one-to-many, many-to-many), implementing FastAPI dependency injection, or migrating schemas. Covers both sync Session and…
fastapi-backend
Build production-grade FastAPI backends with SQLModel, Pydantic, and JWT authentication. Use this skill when building REST APIs, integrating with Neon PostgreSQL, implementing Better Auth JWT verification, or creating CRUD endpoints. Includes patterns for audit logging, worker/agent parity, and OpenAPI documentation.