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 Primadetaautomation/primadata-marketplace --skill supabase-rls-fixgit clone --depth 1 https://github.com/Primadetaautomation/primadata-marketplaceWrote 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/primadetaautomation/primadata-marketplace/supabase-rls-fix)<a href="https://agentmods.dev/skills/primadetaautomation/primadata-marketplace/supabase-rls-fix"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/supabase-rls-fix/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/primadetaautomation/primadata-marketplace/supabase-rls-fix"><img src="https://agentmods.dev/badge/skills/primadetaautomation/primadata-marketplace/supabase-rls-fix.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.00032 | $0.01887 |
| Opus 5 | $0.00016 | $0.00944 |
| Sonnet 5 | $0.00006 | $0.00377 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
supabase-rls-fix 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.
How it starts
The opening of the file, as written. The whole thing — 286 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase RLS Fix Skill
When to Use This Skill
Activate this skill when you encounter:
- "relation does not exist" errors with user/tenant tables
- "Tenant or user not found" errors in background jobs
- System processes failing due to missing user context
- RLS policies blocking scheduled tasks
- Need to add RLS to new tables
Quick Fixes
🚨 Fix 1: Missing user_tenants Table
If you get: ERROR: relation "user_tenants" does not exist
Create compatibility view:
-- Run in Supabase SQL Editor
DROP VIEW IF EXISTS user_tenants CASCADE;
CREATE OR REPLACE VIEW user_tenants AS
SELECT * FROM tenant_memberships;
GRANT SELECT ON user_tenants TO authenticated;
GRANT SELECT ON user_tenants TO anon;
🚨 Fix 2: System Process Failures
If background jobs fail with "Tenant or user not found":
Update the function to handle system processes:
CREATE OR REPLACE FUNCTION get_current_user_tenant_ids()
RETURNS UUID[] AS $$
DECLARE
current_user_id_str TEXT;
current_user_uuid UUID;
tenant_ids UUID[];
BEGIN
-- Get current user setting (may be null for system processes)
current_user_id_str := current_setting('app.current_user_id', true);
-- If no user context (system process/background job), return empty array
IF current_user_id_str IS NULL OR current_user_id_str = '' THEN
RETURN ARRAY[]::UUID[];
END IF;
-- Try to convert to UUID
BEGIN
current_user_uuid := current_user_id_str::UUID;
EXCEPTION WHEN OTHERS THEN
RETURN ARRAY[]::UUID[];
END;
-- Get user's tenant IDs
SELECT ARRAY_AGG(tenant_id) INTO tenant_ids
FROM tenant_memberships
WHERE user_id = current_user_uuid;
RETURN COALESCE(tenant_ids, ARRAY[]::UUID[]);
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;
Permanent Solution: Standardized RLS Functions
Step 1: Create Helper Functions
-- Helper 1: Detect system processes
CREATE OR REPLACE FUNCTION is_system_process()
RETURNS BOOLEAN AS $$
BEGIN
-- Check if explicitly marked as system process
IF current_setting('app.is_system', true) = 'true' THEN
RETURN true;
END IF;
-- Check if no user context (also system process)
IF current_setting('app.current_user_id', true) IS NULL OR
current_setting('app.current_user_id', true) = '' THEN
RETURN true;
END IF;
RETURN false;
END;
$$ LANGUAGE plpgsql IMMUTABLE SECURITY DEFINER;
-- Helper 2: Universal access checker
CREATE OR REPLACE FUNCTION can_access_row(
p_user_id UUID DEFAULT NULL,
p_tenant_id UUID DEFAULT NULL
)
RETURNS BOOLEAN AS $$
DECLARE
v_current_user_id UUID;
v_current_tenant_id UUID;
BEGIN
-- System processes always have access
IF is_system_process() THEN
RETURN true;
END IF;
-- Get current user/tenant from session
BEGIN
v_current_user_id := current_setting('app.current_user_id', true)::UUID;
EXCEPTION WHEN OTHERS THEN
v_current_user_id := NULL;
END;
BEGIN
v_current_tenant_id := current_setting('app.current_tenant_id', true)::UUID;
EXCEPTION WHEN OTHERS THEN
v_current_tenant_id := NULL;
END;
-- Check user match
IF p_user_id IS NOT NULL AND v_current_user_id = p_user_id THEN
RETURN true;
END IF;
-- Check tenant match
IF p_tenant_id IS NOT NULL AND v_current_tenant_id = p_tenant_id THEN
RETURN true;
END IF;
-- Check if user belongs to tenant
IF p_tenant_id IS NOT NULL AND v_current_user_id IS NOT NULL THEN
RETURN EXISTS (
SELECT 1 FROM tenant_memberships
WHERE user_id = v_current_user_id
AND tenant_id = p_tenant_id
AND status = 'ACTIVE'
);
END IF;
RETURN false;
END;
$$ LANGUAGE plpgsql SECURITY DEFINER;
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.
- 11d ago First seen · 286 lines · 32 tokens per session scan A fabc37acd44f
supabase-rls-fix is a skill published in the GitHub repository Primadetaautomation/primadata-marketplace (5 stars, last pushed 9mo ago), licensed MIT. It adds 32 tokens to every session and 1,887 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…