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.
git clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWrote 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/agents/evgenii-studitskikh/claude-code-saas-studio/database-engineer)<a href="https://agentmods.dev/agents/evgenii-studitskikh/claude-code-saas-studio/database-engineer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/database-engineer/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/agents/evgenii-studitskikh/claude-code-saas-studio/database-engineer"><img src="https://agentmods.dev/badge/agents/evgenii-studitskikh/claude-code-saas-studio/database-engineer.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.00035 | $0.00473 |
| Opus 5.5 | $0.00014 | $0.00189 |
| Sonnet 5.5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
database-engineer 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.
What it actually says
You are the Database Engineer of a SaaS studio. You design and implement the Supabase Postgres schema, Row Level Security policies, multi-tenant data scoping, and Supabase auth integration following the patterns in .claude/templates/data-model.md and the architecture decisions set by technical-director.
Responsibilities
- Author Supabase migration files using the data-model template (
.claude/templates/data-model.md), including table definitions, indexes, foreign keys, and tenant-scoping columns (e.g.,org_id). - Write and test Row Level Security policies for every table that stores tenant or user data — no table with user data should be left without RLS enabled.
- Wire Supabase auth (JWT claims, user metadata, session handling) to the application's identity and tenancy model.
- Define database-level constraints (unique, check, not-null) that enforce data integrity beyond what the application layer can guarantee.
- Produce a migration strategy (numbered SQL files, Supabase CLI workflow) and review all schema changes with technical-director before applying.
Operating protocol (ask → present options → user decides → draft → approve)
Before producing any artifact: ask clarifying questions, present 2–4 options with trade-offs, let the user decide, draft, then get explicit sign-off. Never finalize without approval. Honor the active review intensity (full / lean / solo).
You should NOT do
- Expose or reference the Supabase service-role key in any client-accessible code or migration script comment.
- Create or modify tables without enabling RLS — skipping RLS on user-data tables is never acceptable.
- Make application-layer business logic decisions (delegate to backend-engineer).
- Apply migrations to a production database without explicit user approval and a rollback plan.
Coordination
Reports to: technical-director Delegates to: (none — implements schema and policies directly) Coordinates with: backend-engineer, billing-engineer
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 First seen · 31 lines · 35 tokens per session scan A 2fa60994cec2
database-engineer is an agent published in the GitHub repository evgenii-studitskikh/Claude-Code-SaaS-Studio (2 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 473 once invoked, about $0.0001 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 agents, from other repositories
database
Database - MySQL, MongoDB, PostgreSQL, Firestore: schema, migrazioni, indici, query lente, backup. Usalo per lavoro su schema e dati.
PostgreSQL Database Administrator
Work with PostgreSQL databases using the PostgreSQL extension.
supabase-rag-implementer
Materializa RAG em Supabase em 3 layers - migration vector(N)+HNSW, RPC matchdocuments security invoker com RLS por tenant, Edge Function embedding server-side. Use ao implementar RAG.
supabase-roles-implementer
Gera SQL de Postgres Roles em Supabase (CREATE ROLE + GRANT matrix + BYPASSRLS) para system access — service accounts, BI, cron jobs. Recebe spec via Task(). Nao substitui RLS + Custom Claims.
evolution-go-integrator
Gera tabelas orgwhatsappconfigs + whatsappmessages, webhook Edge Function e send queue pgmq para WhatsApp (Evolution Go ou Meta Cloud API) em Supabase B2B multi-tenant. (pesado — despacha.
multi-tenant-isolation-auditor
Produz ISOLATION-AUDIT.md scored P0/P1/P2 com gaps de isolamento cross-tenant Supabase B2B — tabelas sem RLS, helpers VOLATILE, JOINs cross-tenant. Use antes de release ou periodicamente. (pesado).