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 roedyrustam/vibes-plug --skill supabase-security-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/supabase-security-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/supabase-security-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/supabase-security-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/roedyrustam/vibes-plug/supabase-security-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/supabase-security-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00075 | $0.02645 |
| Opus 5.5 | $0.00030 | $0.01058 |
| Sonnet 5.5 | $0.00015 | $0.00529 |
| Haiku 4.5 | $0.00007 | $0.00265 |
Grade A, and why
supabase-security-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 2d 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 — 259 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase Security Expert (2026 Edition — Auth v3 / PKCE)
English
Orchestration & Integration
- Database Architecture & ORM:
database-orm-expert,saas-multi-tenant,saas-billing - Identity & Authentication:
authentication-identity-expert,zero-trust-secret-vault - Threat Defense & Pen-Testing:
autonomous-red-teamer,rate-limit-abuse-prevention,prompt-injection-firewall - Frontend & Storage Integration:
senior-frontend,nextjs-app-router-expert,file-upload-media-expert - Lifecycle & Governance:
production-ready-hardener,brainstorming,zero-to-prod-orchestrator,session-memory-manager
Description
Expert guide for auditing and hardening Supabase applications. Covers Row Level Security (RLS), Supabase Auth v3 (PKCE flow), API key hygiene, data leakage prevention, Supabase Linter, and production security checklists.
Trigger Conditions
- Auditing RLS policies for correctness and security gaps.
- Setting up Supabase Auth v3 with PKCE flow (replaces implicit flow).
- Reviewing API key usage (anon key vs. service role key).
- Preventing data leakage from misconfigured policies.
- Running Supabase Linter (
supabase lint) for automated security checks. - Implementing user roles and access control in a Supabase project.
Supabase Auth v3 — PKCE Flow (2026 Default)
Supabase Auth v3 now uses PKCE (Proof Key for Code Exchange) as the default flow for all OAuth and magic link authentication — replacing the older implicit flow:
// supabase/client.ts — v3 client setup
import { createBrowserClient } from '@supabase/ssr';
export const supabase = createBrowserClient(
process.env.NEXT_PUBLIC_SUPABASE_URL!,
process.env.NEXT_PUBLIC_SUPABASE_ANON_KEY!,
{
auth: {
flowType: 'pkce', // Default in Auth v3
autoRefreshToken: true,
persistSession: true,
detectSessionInUrl: true,
}
}
);
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.
- 2d ago Changed · +7 lines · +75 tokens per session bbd66d5f579b
- 3d ago Changed · +2 lines · -75 tokens per session 525d28e8bbcf
- 6d ago Changed 7383724737de
- 15d ago Changed 21513969f2a7
- 20d ago Changed a088cf517990
- 21d ago Changed ec0deedd5e40
- 23d ago Changed · -6 lines · +62 tokens per session 82e4d37ac11d
- 25d ago Changed · +6 lines · -62 tokens per session c965a4834973
- 1mo ago Changed 2ff89b5a93e3
- 1mo ago First seen · 250 lines · 75 tokens per session scan A b92d10826c87
supabase-security-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed yesterday), licensed MIT. It adds 75 tokens to every session and 2,645 once invoked, about $0.0003 per session on Opus 5.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
postgresql-table-design
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
deprecation-and-migration
Manages deprecation and migration. Use when removing old systems, APIs, or features. Use when migrating users from one implementation to another. Use when migrating a database schema in production, such as renaming or dropping a column without downtime (expand/contract). Use when deciding whether to maintain or sunset…
ai-engineering-toolkit
Overview of six AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
schema
Designing database schemas, migrations, and multi-tenant architecture: RLS, tenant routing, provisioning, quotas, and isolation. Not for query-plan tuning (Tuner).
seek
Designing search engines and vector DBs for full-text, vector, and hybrid retrieval, including permission-aware retrieval for multi-tenant or per-role corpora. Use for search design, index optimization, the RAG retrieval layer, or deciding where ACL filtering belongs in the query path.
system-and-data-design
Decide whether the system will hold, and where the data lives: requirements and load first, then back-of-the-envelope numbers, building blocks (cache, queue, load balancer, CDN), and the data layer in depth — storage engines, indexes, replication, partitioning, transactions and consistency, batch vs stream. Use when…