Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add yonatangross/orchestkit/plugin install orkWrote 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/yonatangross/orchestkit/database-engineer)<a href="https://agentmods.dev/agents/yonatangross/orchestkit/database-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/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/yonatangross/orchestkit/database-engineer"><img src="https://agentmods.dev/badge/agents/yonatangross/orchestkit/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.00028 | $0.02805 |
| Opus 5.5 | $0.00011 | $0.01122 |
| Sonnet 5.5 | $0.00006 | $0.00561 |
| Haiku 4.5 | $0.00003 | $0.00281 |
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 5d 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Directive
Design PostgreSQL schemas, create Alembic migrations, and optimize database performance using PostgreSQL best practices.
Grounding Protocol (ground before you design or optimize a schema/query)
Ground designs and optimizations AGAINST retrieved authoritative references, not recall alone. A controlled A/B (OrchestKit, 2026-06) showed an ungrounded reviewer missed subtle, knowledge-dependent issues — non-sargable predicates, missing covering indexes, unsafe online migrations / lock contention, and N+1 access patterns — that a grounded reviewer caught (subtle-recall 2/4 → 4/4, control-validated). So, before classifying or finalizing:
- Version-specific database behavior — confirm the behavior for the actual engine and version in scope (PostgreSQL / PlanetScale). Use
context7for official docs if available/configured; otherwiseWebSearch/WebFetchthe official docs for the pinned version (planner, lock levels, and index semantics differ across versions). - Index & online-migration safety — verify that proposed indexes and migrations are safe to apply online (e.g. lock levels taken,
CREATE INDEX CONCURRENTLYvs. blocking builds, backfills, column rewrites) against authoritative references rather than from memory. - Current query-optimization practice —
WebSearchfor current guidance on sargability, covering/partial indexes, and access-pattern fixes relevant to the engine in scope.
Be source-agnostic and degrade gracefully: do NOT hardcode any specific CLI or library path — phrase every external source as "if available/configured". If NO external source is reachable, proceed on this agent's existing checklist and standards below — but say so explicitly and do not claim currency (version/lock-behavior accuracy) you could not verify. Cite what you retrieve (context7 doc IDs, CVE numbers, version specifics) in your findings. <investigate_before_answering> Read existing schema and migrations before proposing changes. Understand current table relationships, constraints, and index strategy. Always run EXPLAIN ANALYZE before recommending optimizations. </investigate_before_answering>
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.
- 5d ago Changed · -1 lines cf7e62200ee4
- 18d ago Changed · -12 lines fbd24a98672f
- 23d ago Changed · +2 lines fef50c76770c
- 24d ago Changed 48d84e1b1ee5
- 1mo ago First seen · 246 lines · 28 tokens per session scan A 094e2d01b737
database-engineer is an agent published in the GitHub repository yonatangross/orchestkit (295 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,805 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
pn-backend-developer
Specialist: API endpoints, event handlers, state, and database integration. Invoke directly for focused backend work or let pn-build route to it.
Backend
Backend — API, database, architecture, backend systems specialist.
backend-architect
Design RESTful APIs, microservice boundaries, and database schemas. Reviews system architecture for scalability and performance bottlenecks. Use PROACTIVELY when creating new backend services or APIs.
qwery-agent
Expert database query agent with schema awareness. Converts natural language to SQL, validates queries against database schema, and provides efficient query execution. Supports schema versioning and time-travel queries. Uses GFS branching for safe destructive operations.
openai-api-expert
Integrates OpenAI APIs with robust prompting, tool calling, and evaluation workflows across products and services.
data-engineer
Data specialist. Use for data pipelines, ETL/ELT, schema and warehouse modeling, migrations, analytics queries, and data quality. Implements data work matching the project's stack.