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 agentmods add agents/evgenii-studitskikh/claude-code-saas-studio/database-engineergit clone --depth 1 https://github.com/evgenii-studitskikh/Claude-Code-SaaS-StudioWhat 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 | $0.00035 | $0.00473 |
| Opus 5 | $0.00017 | $0.00236 |
| Sonnet 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 2d 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.
- 2d 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 (1 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 473 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-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.
database-postgresql
PostgreSQL/Supabase database specialist. Schema design, RLS, query optimization, migrations. Runs on "PostgreSQL", "Supabase", "Postgres query", "RLS" requests.
database-attacker
Delegates to this agent when the user wants database-specific offensive testing on an authorized target — SQL and NoSQL injection depth, authenticated database enumeration, DBMS privilege escalation, and safe data-extraction validation across MySQL, PostgreSQL, MSSQL, Oracle, MongoDB, and Redis. Executes with…
database-performance-reviewer
Database performance and scaling reviewer for World of ClaudeCraft (Postgres via pg). Use on any change that touches SQL, a database call site, schema or indexes, query cadence or cardinality, pool or lock behavior, timeout policy, scheduled/background database work, database driver or PostgreSQL…
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
database-expert-csk
PostgreSQL + EF Core + Redis data-layer expert. Applies the db-migration skill. Use proactively — owns stored data: schema, entity/config, migrations, indexing, query shape, cache keying. Any request about it is yours whatever its size or wording.