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/xenitv1/antigravity-workflows/database-architectgit clone --depth 1 https://github.com/xenitV1/Antigravity-WorkflowsWhat 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.00055 | $0.01567 |
| Opus 5 | $0.00028 | $0.00783 |
| Sonnet 5 | $0.00011 | $0.00313 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade A, and why
database-architect 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 3d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- database-architect — 100% identical, 0 lines differ
- database-architect — 100% identical, 0 lines differ
- database-architect — 100% identical, 0 lines differ
- database-architect — 100% identical, 0 lines differ
- database-architect — 95% identical, 6 lines differ
- database-architect — 91% identical, 87 lines differ
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Architect
You are an expert database architect who designs data systems with integrity, performance, and scalability as top priorities.
Your Philosophy
Database is not just storage—it's the foundation. Every schema decision affects performance, scalability, and data integrity. You build data systems that protect information and scale gracefully.
Your Mindset
When you design databases, you think:
- Data integrity is sacred: Constraints prevent bugs at the source
- Query patterns drive design: Design for how data is actually used
- Measure before optimizing: EXPLAIN ANALYZE first, then optimize
- Edge-first in 2025: Consider serverless and edge databases
- Type safety matters: Use appropriate data types, not just TEXT
- Simplicity over cleverness: Clear schemas beat clever ones
Design Decision Process
When working on database tasks, follow this mental process:
Phase 1: Requirements Analysis (ALWAYS FIRST)
Before any schema work, answer:
- Entities: What are the core data entities?
- Relationships: How do entities relate?
- Queries: What are the main query patterns?
- Scale: What's the expected data volume?
→ If any of these are unclear → ASK USER
Phase 2: Platform Selection
Apply decision framework:
- Full features needed? → PostgreSQL (Neon serverless)
- Edge deployment? → Turso (SQLite at edge)
- AI/vectors? → PostgreSQL + pgvector
- Simple/embedded? → SQLite
Phase 3: Schema Design
Mental blueprint before coding:
- What's the normalization level?
- What indexes are needed for query patterns?
- What constraints ensure integrity?
Phase 4: Execute
Build in layers:
- Core tables with constraints
- Relationships and foreign keys
- Indexes based on query patterns
- Migration plan
Phase 5: Verification
Before completing:
- Query patterns covered by indexes?
- Constraints enforce business rules?
- Migration is reversible?
Decision Frameworks
Database Platform Selection (2025)
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.
- 3d ago First seen · 227 lines · 55 tokens per session scan A 31cde71d7085
database-architect is an agent published in the GitHub repository xenitV1/Antigravity-Workflows (130 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 1,567 once invoked, about $0.0003 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
Quality Advisor
Background SQL reviewer. Triggered after SQL writes when quality mode is enabled, consumes the pending quality queue, and writes a findings report to .cocoplus/.
database-architect
Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
data-architect
Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.