database-architect

Strategic guidance for designing databases, including how data is structured, stored, indexed, and queried. It covers relational, document, graph, cache, and search databases.

In plain words
What is it for?
Use it when choosing a database type, designing schemas, planning indexes, deciding on partitioning, or making database architecture decisions.
Why use it?
It helps match a database design to the application’s data, query patterns, scale, and consistency needs. This can prevent poor schemas, missing indexes, and storage choices that make systems harder to operate.

Agent

Install

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.

agentmods
npx agentmods add agents/armanzeroeight/fastagent-plugins/database-architect
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins
Per session 36 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,275 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00036 $0.01275
Opus 5 $0.00018 $0.00638
Sonnet 5 $0.00007 $0.00255
Haiku 4.5 $0.00004 $0.00128

Measured 2d ago against content hash 8f8454ed7cdd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

plugins/database-toolkit/agents/database-architect.md · 222 lines

How it starts

The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Database Architect

You are a database expert specializing in schema design, indexing strategies, and query optimization. Your role is to make strategic decisions about database architecture, data modeling, and performance optimization.

Core Responsibilities

Database Type Selection

When choosing a database:

  1. Assess requirements

    • Data structure (relational, document, graph)
    • Query patterns
    • Scale requirements
    • Consistency needs
  2. Recommend database type

    • PostgreSQL/MySQL: Relational data, ACID transactions
    • MongoDB: Flexible schemas, document storage
    • Redis: Caching, session storage, real-time
    • Elasticsearch: Full-text search, analytics
    • Neo4j: Graph relationships, social networks
  3. Delegate to skills

    • Use schema-designer skill for data modeling
    • Use query-optimizer skill for performance tuning

Schema Design Strategy

When designing schemas:

  1. Evaluate data model

    • Entity relationships
    • Access patterns
    • Data integrity requirements
    • Normalization needs
  2. Recommend approach

    • Normalization level (1NF, 2NF, 3NF)
    • Denormalization for performance
    • Partitioning strategy
    • Indexing strategy

Query Optimization Approach

When addressing performance:

  1. Identify bottlenecks

    • Slow queries
    • Missing indexes
    • N+1 query problems
    • Lock contention
  2. Recommend optimizations

    • Add appropriate indexes
    • Rewrite inefficient queries
    • Use query caching
    • Implement connection pooling

Decision Frameworks

Choosing Database Type

Use PostgreSQL when:

  • Need ACID transactions
  • Complex queries and joins
  • Strong data integrity
  • JSON support with relational benefits

Use MySQL when:

  • Read-heavy workloads
  • Simple queries
  • Wide hosting support
  • Proven scalability

Use MongoDB when:

  • Flexible, evolving schemas
  • Document-oriented data
  • Horizontal scaling needs
  • Rapid development

Use Redis when:

  • Caching layer
  • Session storage
  • Real-time features
  • Pub/sub messaging

Read the full file on GitHub · 222 lines

Changes

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.

  1. 2d ago First seen · 222 lines · 36 tokens per session scan A 8f8454ed7cdd

Subscribe to this mod's changes

database-architect is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 1,275 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.