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 kouroshez/coding-os --skill supabasegit clone --depth 1 https://github.com/kouroshez/coding-osWrote 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/kouroshez/coding-os/supabase)<a href="https://agentmods.dev/skills/kouroshez/coding-os/supabase"><img src="https://agentmods.dev/badge/skills/kouroshez/coding-os/supabase.svg" alt="Measured on agentmods" 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.00077 | $0.01329 |
| Opus 5 | $0.00039 | $0.00665 |
| Sonnet 5 | $0.00015 | $0.00266 |
| Haiku 4.5 | $0.00008 | $0.00133 |
Grade A, and why
supabase 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase
Supabase is Postgres with a public API in front of it. That inversion is the whole risk model: the anon key ships to the browser, so the database — not the application — is the security boundary. Row Level Security is not optional hardening; it is the only thing standing between a user and everyone else's rows.
Scan a migration for tables left without RLS:
python3 scripts/check_rls.py supabase/migrations/*.sql
RLS is the security boundary (enable it on every table)
-- Wrong — table is reachable via the anon key with NO policy = fully public
create table notes (id uuid primary key, user_id uuid, body text);
-- Correct — enable RLS, then policies grant the minimum
create table notes (id uuid primary key, user_id uuid references auth.users, body text);
alter table notes enable row level security;
create policy "owner reads own notes" on notes
for select using (auth.uid() = user_id);
create policy "owner writes own notes" on notes
for insert with check (auth.uid() = user_id);
A table created without enable row level security is readable and writable by
anyone holding the anon key — which is every visitor. Enable RLS on every
table in a public schema, then add policies. using filters which rows are
visible/updatable; with check validates rows being inserted/updated. Detail →
references/rls-and-auth.md.
The two keys — never confuse them
anon key → ships to the browser. RLS applies. Safe to expose IF RLS is on.
service_role key → bypasses RLS entirely. SERVER ONLY. Never in client code, never in git.
// Wrong — service_role in the browser = total database access for every visitor
const supabase = createClient(url, SERVICE_ROLE_KEY); // in frontend code
// Correct — anon key client-side (RLS enforced); service_role only in a server/edge function
const supabase = createClient(url, ANON_KEY);
The service_role key bypasses all RLS — leaking it is a full database breach.
It belongs only in server-side code (edge functions, your backend) and a secret
store, never bundled to the client.
What ships with it
5 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.
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 · 109 lines · 77 tokens per session scan A 36b01b9becf9
supabase is a skill published in the GitHub repository kouroshez/coding-os (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 77 tokens to every session and 1,329 once invoked, about $0.0004 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 skills, from other repositories
memstack-security-rls-guardian
Use this skill when creating or altering database tables in Supabase or PostgreSQL projects. Triggers include: CREATE TABLE, ALTER TABLE, migration files, 'RLS', 'row level security', 'new table', 'database schema'. Enforces Row Level Security policies on every table to prevent unauthorized data access. Do NOT use for…
supabase-node
Express/Hono with Supabase and Drizzle ORM.
supabase
Core Supabase CLI, migrations, RLS, Edge Functions.
ring:mapping-service-resources
Mapping a Go service's Service -> Module -> Resource hierarchy for dispatch-layer registration: detects modules and per-module PostgreSQL/MongoDB/RabbitMQ resources, database names, and shared databases, generates MongoDB index migration pairs (.up.json/.down.json), detects existing Postgres migrations, emits an HTML…
saas-multi-tenant
Design and implement multi-tenant SaaS architectures with RLS, tenant isolation, and PostgreSQL / Desain dan implementasikan arsitektur SaaS multi-tenant dengan RLS, isolasi tenant, dan PostgreSQL.
edge-serverless-db-expert
Expert guide for Serverless & Edge Databases (Neon Serverless Postgres, Cloudflare D1, Turso/libsql, Upstash Redis), cold-start mitigation, and connection pooling / Panduan ahli database Serverless & Edge (Neon, Cloudflare D1, Turso, Upstash).