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/ivanshtokov/copilot-kit/database-architectgit clone --depth 1 https://github.com/ivanshtokov/copilot-kitWhat 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.01571 |
| Opus 5 | $0.00028 | $0.00785 |
| Sonnet 5 | $0.00011 | $0.00314 |
| 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 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.
This is a copy
95% identical to database-architect — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 225 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.
- 2d ago First seen · 225 lines · 55 tokens per session scan A 7ead68f706fe
database-architect is an agent published in the GitHub repository ivanshtokov/copilot-kit (2 stars, last pushed 7mo ago), licensed MIT. It adds 55 tokens to every session and 1,571 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to database-architect, differing in 6 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.