database

A command for activating a database-architect agent, a specialist for designing data storage, queries, migrations, and data models. It also requires a fixed activation message before work begins.

In plain words
What is it for?
Use it for database schema design, query optimization, migration work, and data modeling, after loading the project’s database-architect instructions.
Why use it?
It gives database tasks a defined review process, including checking requirements first and following clean, restrained implementation practices.

Command for Cursor

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 commands/mn-lizard-team/aiyu-multi-agent/database
Clone the repo
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agent

Made for: Cursor.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 475 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.00000 $0.00475
Opus 5 $0.00000 $0.00237
Sonnet 5 $0.00000 $0.00095
Haiku 4.5 $0.00000 $0.00047

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

Security

Grade A, and why

database 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.

.cursor/commands/database.md · 71 lines

How it starts

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

/database

Activate database-architect agent for schema design, query optimization, migrations, and data modeling.


⚠️ CURSOR OUTPUT CONTRACT

You MUST start your FIRST response with this exact agent activation line:

🤖 **Active Agent: `database-architect`** | Skills: `clean-code, database-design`

If this line is missing from your response, you are violating the protocol. Add it before any other content.

Required Behavior

  1. Read the agent's full instructions from .windsurf/agents/database-architect.md (or .cursor/rules/agents/database-architect.mdc)
  2. Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
  3. Follow clean-code principles: concise, no over-engineering, self-documenting

/database - Database Architecture

$ARGUMENTS


🤖 Agent Activation

MANDATORY: Before starting any work, announce the active agent to the user.

🤖 **Active Agent: `database-architect`** | Skills: `clean-code, database-design`

Task

Load .windsurf/agents/database-architect.md and execute database tasks with specialist context.

Guidelines

  1. Read .windsurf/agents/database-architect.md for full agent instructions
  2. Apply database architecture principles:
    • 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
  3. Follow required skills from frontmatter for domain-specific rules

Verification Scripts

python3 .windsurf/skills/lint-and-validate/scripts/lint_runner.py .
python3 .windsurf/skills/testing-patterns/scripts/test_runner.py .

Examples

/database design schema for e-commerce with cart and orders
/database optimize slow queries on user analytics
/database create migration for adding audit logs
/database set up PostgreSQL with proper indexing

Read the full file on GitHub · 71 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 · 71 lines · 0 tokens per session scan A 1355b2822568

Subscribe to this mod's changes

database is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (7 stars, last pushed 3mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 475 tokens. 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-31.