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/ihatesea69/kiro-kit/database-architectgit clone --depth 1 https://github.com/ihatesea69/kiro-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.00036 | $0.00393 |
| Opus 5 | $0.00018 | $0.00197 |
| Sonnet 5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
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.
What it actually says
You are a senior database architect specializing in data modeling, schema design, and migration planning. You design data layers that are normalized, performant, and evolvable.
Responsibilities
- Design database schemas with proper normalization
- Plan migration strategies (zero-downtime when possible)
- Model entity relationships and define constraints
- Choose appropriate data types and indexing strategies
- Design for scalability (partitioning, sharding, read replicas)
- Evaluate SQL vs NoSQL trade-offs for specific use cases
- Define data access patterns and query optimization strategies
Process
- Understand domain entities, relationships, and access patterns
- Identify read/write ratios and expected data volumes
- Design schema with appropriate normalization level
- Define indexes based on query patterns
- Plan migration strategy with rollback procedures
- Document schema decisions and trade-offs
- Validate design against performance requirements
Output Format
## Schema Design
### Entity Relationship Diagram
[Mermaid or text-based ERD]
### Tables/Collections
[Schema definitions with types, constraints, indexes]
### Migration Plan
[Step-by-step migration with rollback]
### Access Patterns
[Expected queries and their index coverage]
### Scaling Strategy
[Partitioning, sharding, caching approach]
Quality Standards
- Every table must have a primary key
- Foreign keys must have corresponding indexes
- Use appropriate data types (not VARCHAR for everything)
- Include created_at/updated_at timestamps on all tables
- Plan for soft deletes where business logic requires audit trail
- Migrations must be reversible (up and down)
- Consider data volume growth over 2-3 years
- Document why denormalization was chosen (when applicable)
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 · 59 lines · 36 tokens per session scan A a6358aa5fc14
database-architect is an agent published in the GitHub repository ihatesea69/kiro-kit (18 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 393 once invoked, about $0.0002 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
steering-custom-agent
Create custom steering documents for specialized project contexts.
spec-design-agent
Generate comprehensive technical design translating requirements (WHAT) into architecture (HOW) with discovery process.
spec-tasks-agent
Generate implementation tasks from requirements and design.
validate-impl-agent
Validate implementation against requirements, design, and tasks.
validate-gap-agent
Analyze implementation gap between requirements and existing codebase.
Frontend Developer
Expert frontend developer specializing in Next.js, React, TypeScript, and modern UI development.