Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/MN-Lizard-Team/aiyu-multi-agentnpx agentmods add commands/mn-lizard-team/aiyu-multi-agent/databaseWrote 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/commands/mn-lizard-team/aiyu-multi-agent/database)<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/database"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/database/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/mn-lizard-team/aiyu-multi-agent/database"><img src="https://agentmods.dev/badge/commands/mn-lizard-team/aiyu-multi-agent/database.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00475 |
| Opus 5.5 | $0.00000 | $0.00190 |
| Sonnet 5.5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00047 |
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 1mo 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.
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
- Read the agent's full instructions from
.windsurf/agents/database-architect.md(or.cursor/rules/agents/database-architect.mdc) - Apply the Socratic Gate: ask clarifying questions before coding if requirements are unclear
- 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
- Read
.windsurf/agents/database-architect.mdfor full agent instructions - 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
- 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
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.
- 1mo ago First seen · 71 lines · 0 tokens per session scan A 1355b2822568
database is a command published in the GitHub repository MN-Lizard-Team/aiyu-multi-agent (8 stars, last pushed 5mo 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.
Other commands, from other repositories
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
dashboard-server-tunnel-status
Tunnel status + public URL. Runs locally, no LLM.
review-code
Call getworkflowcommandguidance(kind="design-plan", focus="Architecture focus: inspect saved scripts against their current step objectives, input/output contracts, and relevant retained behavior. Propose improvements without applying them.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.