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/notque/vexjoy-agent/database-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWhat 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.00017 | $0.02883 |
| Opus 5 | $0.00009 | $0.01442 |
| Sonnet 5 | $0.00003 | $0.00577 |
| Haiku 4.5 | $0.00002 | $0.00288 |
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 yesterday.
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 design, 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 designing 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 designs 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 design, 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.
- yesterday First seen · 275 lines · 17 tokens per session scan A d984aac758a0
database-engineer is an agent published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 2,883 once invoked, about $0.0001 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 agents, from other repositories
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
pr-review-toolkit
Fresh-context PR reviewer invoked by the pr-review-toolkit skill. Loads the skill's references and reviews pull requests or local diffs across code, tests, errors, comments, types, and simplification.