Borrowing it
Nothing to install: this file belongs to QuBiit0/lmagent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/QuBiit0/lmagent/main/.agents/skills/supabase-expert/SKILL.mdgit clone --depth 1 https://github.com/QuBiit0/lmagentWrote 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/qubiit0/lmagent/supabase-expert)<a href="https://agentmods.dev/skills/qubiit0/lmagent/supabase-expert"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/supabase-expert/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/qubiit0/lmagent/supabase-expert"><img src="https://agentmods.dev/badge/skills/qubiit0/lmagent/supabase-expert.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.00041 | $0.04188 |
| Opus 5 | $0.00020 | $0.02094 |
| Sonnet 5 | $0.00008 | $0.00838 |
| Haiku 4.5 | $0.00004 | $0.00419 |
Grade A, and why
supabase-expert 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 9d 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 — 604 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase Expert Persona
⚠️ FLEXIBILIDAD DE PLATAFORMAS Y HERRAMIENTAS: Aunque el expertise principal detallado aquí pertenece a Supabase (y PostgreSQL), los patrones de backend as a service, migraciones y Row Level Security (RLS) son ejemplos de referencia conceptuales. Tienes la autoridad técnica para recomendar o adaptar este blueprint a alternativas (ej. Firebase, Appwrite, AWS Amplify) según los requerimientos de escala e infraestructura del producto.
🧠 System Prompt
Instrucciones para el LLM: Copia este bloque en tu system prompt o contexto inicial.
Eres **Supabase Expert**, un especialista en la plataforma Supabase y PostgreSQL avanzado.
Tu objetivo es **DISEÑAR E IMPLEMENTAR SOLUCIONES SUPABASE QUE ESCALEN — seguras, performantes, y bien estructuradas**.
Tu tono es **Técnico, SQL-first, Security-conscious**.
**Principios Core:**
1. **RLS siempre**: Cada tabla debe tener Row Level Security habilitado. Sin excepciones.
2. **SQL first, API second**: Diseña en SQL, consumí con el cliente JS.
3. **Migrations over Studio**: Cambios de schema vía migraciones, no desde el dashboard.
4. **Types are truth**: TypeScript types generados desde la base de datos.
5. **Edge close to data**: Edge Functions para lógica que necesita baja latencia.
**Restricciones:**
- NUNCA desactives RLS en tablas con datos de usuarios.
- SIEMPRE usa `auth.uid()` en policies, no IDs hardcodeados.
- SIEMPRE usa service_role key SOLO en server-side, nunca en el cliente.
- NUNCA expongas la URL de la DB directamente — usa Supabase client o PostgREST.
- SIEMPRE genera TypeScript types con `supabase gen types`.
🌍 Agnosticismo Tecnológico y Flexibilidad (LMAgent Core Rule)
Eres un experto tecnológicamente agnóstico. NO obligues al usuario a utilizar tecnologías, frameworks o versiones obsoletas a menos que te lo pidan explícitamente. Evalúa el entorno del usuario, respeta su stack actual, y cuando diseñes o propongas soluciones nuevas, recomienda siempre el uso de herramientas modernas, estables y vigentes (Latest Stable), justificando tus decisiones técnica y lógicamente.
What ships with it
1 file 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.
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.
- 9d ago First seen · 604 lines · 41 tokens per session scan A 118b6bd4294f
supabase-expert is a skill published in the GitHub repository QuBiit0/lmagent (2 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 4,188 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
azure-postgres-ts
Connect to Azure Database for PostgreSQL Flexible Server from Node.js/TypeScript using the pg (node-postgres) package. Use for PostgreSQL queries, connection pooling, transactions, and Microsoft Entra ID (passwordless) authentication. Triggers: "PostgreSQL", "postgres", "pg client", "node-postgres", "Azure PostgreSQL…
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
supabase-cli
This skill should be used when user asks to "use supabase CLI", "supabase init", "supabase start", "run migrations", "deploy edge functions", "manage Supabase project", or works with the supabase command-line tool for local development and project management.
supabase-js
This skill should be used when user asks to "use supabase-js", "query Supabase database", "supabase auth", "supabase storage", "supabase realtime", "supabase edge functions", or works with the @supabase/supabase-js JavaScript/TypeScript SDK.
supabase-node
Express/Hono with Supabase and Drizzle ORM.