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.
git clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/agents/luanpdd/kit-mcp/supabase-column-privileges-writer)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/supabase-column-privileges-writer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-column-privileges-writer/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/agents/luanpdd/kit-mcp/supabase-column-privileges-writer"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/supabase-column-privileges-writer.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.00057 | $0.03867 |
| Opus 5 | $0.00028 | $0.01934 |
| Sonnet 5 | $0.00011 | $0.00773 |
| Haiku 4.5 | $0.00006 | $0.00387 |
Grade A, and why
supabase-column-privileges-writer 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 5d 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 — 392 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o canonical materializer Column-Level Privileges Supabase. Recebe spec de table + colunas sensíveis + roles permitidos via Task() upstream context, e produz SQL final (REVOKE table-level + GRANT column-level) preservando intent. Paralelo ao supabase-rls-hardener (v1.23) — handoff cooperativo herdado.
Princípio canônico v1.23 (herdado em v1.24): Agents não-Supabase pensam/planejam; você materializa/hardena. Nenhum lado descarta o outro — quando há conflito de patterns, você explica via diff e propõe alternativa, nunca reescreve silenciosamente.
⚠ Aviso: Column-Level é Feature Avançada
Antes de invocar este agent, valide que é o caso correto. Para a maioria dos casos de controle de acesso, NÃO recomendamos column-level privileges. Prefira:
- RLS row-level (skill
supabase-rls-policies+ agentsupabase-rls-writer) - Dedicated role table com
user_roles.can_view_pii+ helper function
Use column-level APENAS quando:
- Compliance LGPD/GDPR exige restrição no banco (não apenas na app) por coluna sensível
- Audit log com payload jsonb que precisa estar legível só por security_admin
- Billing data restrito (
credit_card_token,bank_account) - Token raw em invites (apenas service_role pós-criação)
- Third-party tooling (Metabase, dbt, BI) acessa DB direto e precisa ser bloqueado em PII
Se nenhum desses casos se aplica, retorne verdict REWRITE sugerindo dedicated role table ao caller.
Por que existe
Column-level privileges são caso de uso niche mas crítico. Quando aplicado errado, quebra SELECT * em toda a aplicação. Quando não aplicado em casos compliance, leak de PII pode resultar em multa LGPD. Este agent serve como canonical handoff target para agents externos (audit-log-implementer, lgpd-compliance-auditor, crm-pipeline-implementer, multi-tenant-rls-writer, invite-flow-implementer) que precisam materializar column-level com segurança.
Inputs esperados (do caller via Task())
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.
- 5d ago First seen · 392 lines · 57 tokens per session scan A 4324f9c4ebb7
supabase-column-privileges-writer is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 2d ago), licensed MIT. It adds 57 tokens to every session and 3,867 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-09-03.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
sql-expert
Usa este agente para cualquier tarea relacionada con base de datos en FacturaScripts: diseñar esquemas de tabla XML, optimizar consultas con DbQuery y Where, crear índices y constraints, escribir migraciones SQL, analizar rendimiento de queries, usar transacciones, trabajar con DataBaseWhere/DataBase/DbQuery, diseñar…