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 Ozzeron/prompt-pack --skill postgres-supabasegit clone --depth 1 https://github.com/Ozzeron/prompt-packWrote 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/ozzeron/prompt-pack/postgres-supabase)<a href="https://agentmods.dev/skills/ozzeron/prompt-pack/postgres-supabase"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/postgres-supabase/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/ozzeron/prompt-pack/postgres-supabase"><img src="https://agentmods.dev/badge/skills/ozzeron/prompt-pack/postgres-supabase.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.00092 | $0.02220 |
| Opus 5.5 | $0.00037 | $0.00888 |
| Sonnet 5.5 | $0.00018 | $0.00444 |
| Haiku 4.5 | $0.00009 | $0.00222 |
Grade A, and why
postgres-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 1mo 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 — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postgres + Supabase
You work with Supabase: Postgres database, auth, storage, edge functions. This skill captures the platform-specific decisions and traps that the generic database skills don't cover. Covers self-hosted Postgres too where it overlaps.
When to use
- Designing or modifying tables on a Supabase project
- Writing or debugging RLS policies
- Setting up auth.users → public schema integration
- Migration workflow (CLI, dashboard, custom scripts)
- Schema cache issues, PostgREST quirks
- Storage bucket policies
Do not invoke for generic schema design (use architecture/database-schema) or for
non-Postgres databases.
Scope
In scope:
- RLS policy design (
SELECT,INSERT,UPDATE,DELETE, withUSINGandWITH CHECK) auth.usersintegration: triggers to mirror intoprofiles, FK setup- Postgres-specific features:
jsonb, partial indexes, generated columns, materialized views - PostgREST schema cache and reload (
NOTIFY pgrst, 'reload schema') - Supabase migration workflows (
supabase migration new, custom apply scripts, dashboard) - Storage bucket creation and access policies
- Edge functions ↔ DB integration
Out of scope:
- Pure SQL query tuning (use
review/database-review) - Frontend Supabase client patterns
Inherits
architecture/database-schema— base conventions.architecture/database-migrations— base migration safety.meta/engineering-principlesmeta/reuse-before-create— before writing a new RLS policy, helper function, or auth predicate, check existing policies andauth.*helpers for one to reuse or extend.meta/token-discipline
Token discipline (specific)
- Read the project's
supabase/migrations/directory — last 3–5 files only. - Read
supabase/config.tomlonce if it exists. - For RLS questions: read the relevant table's existing policies via SQL or migration; do not re-read the whole RLS history.
- Skip generated TypeScript types unless types are part of the question.
What ships with it
2 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.
- 1mo ago Changed · -44 lines · +65 tokens per session 94edae74e6ba
- 1mo ago First seen · 278 lines · 27 tokens per session scan A f0848140e38b
postgres-supabase is a skill published in the GitHub repository Ozzeron/prompt-pack (8 stars, last pushed 1mo ago), licensed MIT. It adds 92 tokens to every session and 2,220 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
db-context-postgres
Validate that a non-Supabase Postgres database (Cloud SQL, RDS, self-hosted) is reachable, introspect a scoped subset of its schema, and persist it as DBCONTEXT.md. Read-only, opt-in. Use when work touches that database and planning needs verified schema, or DBCONTEXT.md is stale. Do not use without a task (run…
db-context-supabase
Validate that a Supabase MCP server is reachable, introspect a subset of the database (tables, columns, RLS policies), and persist it as DBCONTEXT.md. Read-only, never destructive SQL. Falls back to the local Supabase CLI when no MCP server is reachable. Use when the task touches Supabase data, schema or RLS and…
agent-database-reviewer
PostgreSQL database specialist for query optimization, schema design, security, and performance. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance. Incorporates Supabase best practices.
sql_mastery
CREATE OR REPLACE PROCEDURE sprefreshattributiondaily() LANGUAGE plpgsql AS $$ BEGIN -- 1. Truncate Staging TRUNCATE TABLE stgdailytraffic.
postgresql
Design a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.
postgresql-table-design
Use this skill when designing or reviewing a PostgreSQL-specific schema. Covers best-practices, data types, indexing, constraints, performance patterns, and advanced features.