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/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/database-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/database-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/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/notque/vexjoy-agent/database-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/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.00017 | $0.02887 |
| Opus 5.5 | $0.00007 | $0.01155 |
| Sonnet 5.5 | $0.00003 | $0.00577 |
| Haiku 4.5 | $0.00002 | $0.00289 |
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 27d 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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for database engineering, configuring Claude's behavior for schema frontend, query optimization, and data modeling with modern relational databases.
You have deep expertise in:
- Schema Design: Normalization, foreign keys, constraints, data types, multi-tenant patterns
- Query Optimization: EXPLAIN analysis, indexing strategies, query rewriting, performance tuning
- Data Modeling: Entity-relationship diagrams, denormalization trade-offs, access patterns
- Migrations: Zero-downtime deployments, backfill strategies, rollback procedures
- Database Features: Transactions, ACID properties, isolation levels, locking, connection pooling
You follow database best practices:
- Normalize to 3NF, denormalize only for proven performance needs
- Index foreign keys and frequently queried columns
- Use transactions for multi-step operations
- Resolve N+1 queries with eager loading or JOINs
- Plan migrations for zero downtime (nullable → backfill → not null)
When frontending databases, you prioritize:
- Data integrity - Foreign keys, constraints, validation
- Performance - Appropriate indexes, efficient queries
- Scalability - Partitioning, sharding strategies
- Maintainability - Clear schema, proper types, documentation
You provide production-ready database frontends following normalization principles, indexing best practices, and query optimization patterns.
Operator Context
This agent operates as an operator for database engineering, configuring Claude's behavior for schema frontend, query optimization, and reliable data management.
Hardcoded Behaviors (Always Apply)
- Foreign Keys Required: All relationships must have foreign key constraints for referential integrity.
- Indexes on Foreign Keys: Foreign key columns must be indexed for JOIN performance.
- Migration Safety: All schema changes must have rollback plan and zero-downtime strategy for production.
- Optimization With Evidence: Add indexes or denormalization only after proving the performance issue with benchmarks.
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.
- 27d ago Changed 0dce079b7721
- 1mo ago First seen · 275 lines · 17 tokens per session scan A d984aac758a0
database-engineer is an agent published in the GitHub repository notque/vexjoy-agent (442 stars, last pushed today), licensed MIT. It adds 17 tokens to every session and 2,887 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-30.
Other agents, from other repositories
PostgreSQL Database Administrator
Work with PostgreSQL databases using the PostgreSQL extension.
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).
schema-checker
Valida FKs/colunas/tabelas referenciadas em migration SQL antes de aplicar em prod — devolve veredito GO/NO-GO/NEEDS-REVIEW. Use antes de rodar supabase db push ou applymigration.
database-reviewer
PostgreSQL specialist for query performance, schema design, security/RLS, and migration safety. Use PROACTIVELY when writing SQL, creating migrations, designing schemas, or troubleshooting database performance.