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 komunite/tezgah --skill saas-databasegit clone --depth 1 https://github.com/komunite/tezgahWrote 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/komunite/tezgah/saas-database)<a href="https://agentmods.dev/skills/komunite/tezgah/saas-database"><img src="https://agentmods.dev/badge/skills/komunite/tezgah/saas-database.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.00113 | $0.02595 |
| Opus 5 | $0.00056 | $0.01298 |
| Sonnet 5 | $0.00023 | $0.00519 |
| Haiku 4.5 | $0.00011 | $0.00260 |
Grade A, and why
saas-database 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 8d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS Database — Supabase Veritabanı Altyapısı
Bu skill, bir SaaS uygulamasının veritabanı katmanını kurar. Veritabanı uygulamanın belleğidir — şema kararları, güvenlik politikaları ve bağlantı stratejisi ilk günden doğru kurulmalıdır.
Bağımlılık: Bu skill saas-launcher orkestratör skill'inin Faz 2'sinin derinleştirilmiş versiyonudur. Bağımsız olarak da kullanılabilir.
Bağlı skill'ler:
- saas-auth — Kullanıcı modeli veritabanında tanımlanır. Auth, kullanıcı kaydını burada oluşturur.
- saas-payments — Abonelik ve plan bilgileri veritabanında saklanır.
- saas-storage — Dosya metadata'sı veritabanında, dosyanın kendisi Supabase Storage'da saklanır.
Supabase Proje Kurulumu
İlk Adımlar
- https://supabase.com adresinden hesap oluştur
- Yeni proje oluştur — proje adı, veritabanı şifresi ve bölge seç
- Bölge seçimi: Kullanıcıların çoğunluğuna en yakın bölge. Türkiye için
eu-central-1(Frankfurt) önerilir - Dashboard'dan proje URL'si ve anon key'i al
.env.localdosyasına ekle:NEXT_PUBLIC_SUPABASE_URL— proje URL'si (public, client'ta kullanılır)NEXT_PUBLIC_SUPABASE_ANON_KEY— anonim anahtar (public, RLS ile korunur)SUPABASE_SERVICE_ROLE_KEY— servis anahtarı (gizli, sadece server-side)
Kritik: SUPABASE_SERVICE_ROLE_KEY asla NEXT_PUBLIC_ prefix'i almamalı. Bu anahtar RLS'i bypass eder — client'a sızarsa tüm veriye erişim açılır.
Supabase Client Kurulumu
İki farklı client oluştur:
Browser client (client component'ler için): Anon key ile çalışır, RLS kurallarına tabidir. Kullanıcının kendi verisine erişim için.
Server client (API route'ları ve server component'ler için): Service role key ile çalışır, RLS'i bypass eder. Admin işlemleri, webhook handler'lar ve veri migration'ları için.
Middleware client: Oturum yenileme ve auth kontrolü için. Edge Runtime uyumlu olmalı.
Her client'ı ayrı bir dosyada tanımla ve projede tek yerden import et. Client'ları her dosyada yeniden oluşturma.
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.
- 8d ago First seen · 190 lines · 113 tokens per session scan A 83de5c9140fe
saas-database is a skill published in the GitHub repository komunite/tezgah (90 stars, last pushed 5mo ago), licensed MIT. It adds 113 tokens to every session and 2,595 once invoked, about $0.0006 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-08-30.
Other skills, from other repositories
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
supabase
Use when doing ANY task involving Supabase: Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues, supabase-js, @supabase/ssr, RLS, schema migrations, CLI, MCP server. Includes security checklist.
Prisma Query Optimizer
Query optimization and N+1 detection.
dotcanvas
Author and edit a Grida .canvas board — a .canvas.json manifest plus document files (references, generated images, notes) placed on an infinite canvas. Use when working on a .canvas bundle or arranging visuals/design work spatially. For a linear deck/presentation, use the slides skill instead.
slides
Build a Grida slides deck — a .canvas bundle in slides mode whose pages are SVG documents (16:9, one SVG per slide). Use when creating a presentation, pitch deck, slideshow, or talk.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…