skill-supabase-rls

skill-supabase-rls is a skill for Codex from IAPro-Community/Orquestrador-Maestro. It costs 59 tokens per session (1,034 once invoked), scanned A, original, Apache-2.0.

Guidance for protecting data in Supabase and PostgreSQL with Row Level Security (RLS), a database feature that controls which users can read or change each row.

In plain words
What is it for?
It is for designing and reviewing access policies, storage rules, database migrations, indexes, and tests that check both allowed and denied access.
Why use it?
It helps prevent one SaaS customer or tenant from accessing another customer’s data and clarifies limits around privileged service accounts.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Good fit It is for designing and reviewing access policies, storage rules, database migrations, indexes, and tests that check both allowed and denied access.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/iapro-community/orquestrador-maestro/skill-supabase-rls
Install

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.

Any agent
npx skills add IAPro-Community/Orquestrador-Maestro --skill skill-supabase-rls
Clone the repo
git clone --depth 1 https://github.com/IAPro-Community/Orquestrador-Maestro

Made for: Codex.

Wrote 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.

agentmods badge for skill-supabase-rls

README.md
[![agentmods](https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-supabase-rls/github.svg)](https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-supabase-rls)
Your own site
<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-supabase-rls"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-supabase-rls/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.

agentmods 80×15 button for skill-supabase-rls

Your own site · 80×15
<a href="https://agentmods.dev/skills/iapro-community/orquestrador-maestro/skill-supabase-rls"><img src="https://agentmods.dev/badge/skills/iapro-community/orquestrador-maestro/skill-supabase-rls.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,034 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00059 $0.01034
Opus 5 $0.00030 $0.00517
Sonnet 5 $0.00012 $0.00207
Haiku 4.5 $0.00006 $0.00103

Measured 11d ago against content hash be10ce3c3cb9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

skill-supabase-rls 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 11d 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.

codex/skills/skill-supabase-rls/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

skill-supabase-rls

Authorization gate

Use this skill for projects the user owns or is authorized to modify. For production databases, do not run migrations, resets, destructive SQL, or policy changes without explicit approval in the current task.

Record:

  • Project and environment: local, staging, preview, or production.
  • Tables, schemas, buckets, and tenants in scope.
  • Whether changes are advisory, migration-ready, or approved for execution.

Core rules

  1. Enable RLS on every user-facing table in exposed schemas.
  2. Browser clients must use anon/user auth, never service-role keys.
  3. Service-role keys are allowed only in server functions, controllers, jobs, or trusted backends.
  4. Policies must include user ownership, tenant membership, or explicit role checks.
  5. Admin cross-tenant reads should go through backend routes or RPC with explicit authorization.
  6. Add indexes that match policy predicates and dashboard filters.
  7. Avoid new select('*') reads in application code when sensitive columns exist.
  8. Test positive and negative access cases before claiming security is complete.
  9. Remember that after RLS is enabled, API access with browser-safe keys returns no rows until explicit policies exist.
  10. For SQL-created tables in exposed schemas, enable RLS deliberately; do not rely on dashboard defaults.

Severity and gates

  • Critical: service-role key exposed to client code, RLS disabled on user-facing sensitive tables, cross-tenant read/write, public write access to sensitive data. Block release.
  • High: missing tenant predicate, admin bypass without server-side authorization, storage bucket policy exposing private files, unsafe SECURITY DEFINER function. Block merge until fixed or risk-accepted.
  • Medium: missing policy indexes, broad select('*'), ambiguous anonymous access, missing negative tests. Require ticketed remediation.
  • Low/Info: naming, documentation, policy simplification, performance tuning without direct exposure. Track without blocking.

Read the full file on GitHub · 133 lines

Files

What ships with it

4 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.

Changes

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.

  1. 11d ago First seen · 133 lines · 59 tokens per session scan A be10ce3c3cb9

Subscribe to this mod's changes

skill-supabase-rls is a skill published in the GitHub repository IAPro-Community/Orquestrador-Maestro (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,034 once invoked, about $0.0003 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-30.