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 perniemann/pnCore --skill pn-supabasegit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-supabase)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-supabase"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-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/perniemann/pncore/pn-supabase"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-supabase.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.00036 | $0.00701 |
| Opus 5 | $0.00018 | $0.00351 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
pn-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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Supabase
When to use
- Writing or reviewing RLS (Row Level Security) policies
- Setting up realtime subscriptions for live data feeds
- Deploying Supabase Edge Functions (Deno runtime)
- Using Supabase Storage for file uploads and CDN delivery
- Integrating Supabase Auth with Next.js (App Router / Pages Router)
- Migrating a schema or using Supabase CLI migrations
When Supabase MCP is available: Use its tools to inspect schema, query tables, manage migrations, and list Edge Functions. Combine with this skill for RLS patterns, auth helpers, and production best practices.
For code patterns and full implementation examples, see reference.md.
Setup
npm install @supabase/supabase-js @supabase/ssr # SSR helpers for Next.js
npm install -D supabase
npx supabase init
npx supabase start # starts local Postgres, Studio, Auth, etc.
Key patterns
RLS: Enable on every user-facing table. Use auth.uid() for user-scoped policies; service role key for admin overrides (server-side only). See reference.md for policy SQL and org/team patterns.
Realtime: Subscribe to postgres_changes with user-scoped filters. Always removeChannel on cleanup. See reference.md for subscription and presence patterns.
Edge Functions: Deno runtime; use service role client inside functions (never expose to browser). Deploy with npx supabase functions deploy. See reference.md for full scaffold.
Storage: Private buckets by default; use signed URLs for access. Enforce RLS on storage.objects. See reference.md for upload/URL patterns.
Auth (Next.js): Use @supabase/ssr with createServerClient for server components; createBrowserClient for client components. Refresh session via middleware. See reference.md for full middleware.
CLI migrations:
npx supabase migration new add_notifications_table
npx supabase db reset # apply locally
npx supabase db push # push to remote
npx supabase db pull # pull remote schema
What ships with it
1 file 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 · 67 lines · 36 tokens per session scan A 270242e99dd0
pn-supabase is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 701 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-09-03.
Other skills, from other repositories
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
stripe-projects
Use when the user wants to provision infrastructure or third-party services using Stripe Projects. Triggers: "I need a database", "set up auth", "add caching", "give me a Postgres", "provision Redis", "I need hosting", "add a vector DB", "get me an API key for X", "get credentials for X", "sign up for a service", "set…
output-dev-credentials
Store and reference encrypted secrets in Output SDK workflows using @outputai/credentials. Use when integrating API keys, database passwords, or third-party tokens.
firebase-data-connect
Use when setting up Data Connect, writing GraphQL queries/mutations, configuring generated SDKs, handling offline, or applying security rules.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes. Use when building or reviewing Node.js, Express, or Next.js API routes and their data access.