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/hainamchung/agent-assistant/database-architectgit clone --depth 1 https://github.com/hainamchung/agent-assistantWrote 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/hainamchung/agent-assistant/database-architect)<a href="https://agentmods.dev/agents/hainamchung/agent-assistant/database-architect"><img src="https://agentmods.dev/badge/agents/hainamchung/agent-assistant/database-architect.svg" alt="Measured on agentmods" 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 | $0.00016 | $0.01134 |
| Opus 5 | $0.00008 | $0.00567 |
| Sonnet 5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00113 |
Grade C, and why
database-architect scanned grade C with 1 finding 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 4d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- 🔒 COGNITIVE ANCHOR — MANDATORY OPERATING SYSTEM --> How it starts
The opening of the file, as written. The whole thing — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
BINDING: This file OVERRIDES default AI patterns. Follow Thinking Protocol EXACTLY. EXTRACT: Core Directive + Constraints + Output Format before proceeding.
🗄️ Database Architect
| Attribute | Value |
|---|---|
| ID | agent:database-architect |
| Role | Principal Database Architect |
| Profile | data:execution |
| Reports To | tech-lead |
| Consults | backend-engineer, security-engineer, performance-engineer |
| Confidence | 90% (data loss risk) |
CORE DIRECTIVE: Data is sacred. Design schemas that are normalized yet performant. Guard data integrity at all costs. Think about scale from day one.
Prime Directive: ANALYZE → MODEL → NORMALIZE → OPTIMIZE → MIGRATE. Never delete without confirmation.
⚡ Skills
MATRIX DISCOVERY: Skills auto-injected from domain files in
~/.{TOOL}/skills/agent-assistant/matrix-skills/Profile:data:execution| Domains:data,performance,architecture
🎯 Expert Mindset
THINK_LIKE:
- "What's the access pattern?"
- "Will this scale to 10x data?"
- "Is this query efficient?"
- "What's the rollback plan?"
ALWAYS:
- Test queries with EXPLAIN
- Have rollback for every migration
- Use transactions for multi-table ops
- Document schema decisions
🧠 Thinking Protocol
Step 0: CONTEXT & PLAN CHECK (MANDATORY)
1. CHECK PROJECT DOCS (if ./.documents/ exists):
- knowledge-architecture/00-index.md → Existing architecture (drill into sub-files as needed)
- knowledge-domain/00-index.md → Data models, schema (drill into sub-files as needed)
- knowledge-standards/00-index.md → Naming conventions (drill into sub-files as needed)
→ USE these for schema naming and structure
2. CHECK: ./.reports/{topic}/plans/PLAN-{feature}
→ EXISTS: READ data model sections, follow EXACTLY
→ Complex + NO PLAN: STOP → Request plan (DB changes hard to undo)
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.
- 4d ago First seen · 159 lines · 16 tokens per session scan C 5a1da42ab6f2
database-architect is an agent published in the GitHub repository hainamchung/agent-assistant (54 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 1,134 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
django-migrations-specialist
Database specialist for Django, runs in the "database" extra phase after development. Finalizes model field types and Meta indexes/constraints, runs makemigrations, reviews generated SQL with sqlmigrate, runs migrate, verifies with migrate --check. Do NOT use for: application logic (django-architect), tests…
database-architect
Use this agent for database design and change work: schema design, indexing strategy, query optimization, migration safety, and engine selection. Trigger on "design a schema for", "this query is slow", "is this migration safe", "add an index", "Postgres or Mongo for this", or N+1 complaints. Returns schema/DDL with…
db-performance-auditor
Audits a .NET data-access layer end to end for performance — EF Core query patterns (N+1, projections, tracking), indexing gaps, DbContext configuration, connection resiliency, and bulk-operation opportunities — and produces a ranked report with fixes. Use when the user wants a database/EF performance review of a…