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/myrtlepn/gran-maestro/schema-designergit clone --depth 1 https://github.com/myrtlepn/gran-maestroWrote 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/myrtlepn/gran-maestro/schema-designer)<a href="https://agentmods.dev/agents/myrtlepn/gran-maestro/schema-designer"><img src="https://agentmods.dev/badge/agents/myrtlepn/gran-maestro/schema-designer.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.1 | $0.00000 | $0.01005 |
| Opus 5 | $0.00000 | $0.00502 |
| Sonnet 5 | $0.00000 | $0.00201 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
schema-designer 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 6d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DEPRECATED: 이 파일은 스킬로 전환되었습니다.
skills/schema-designer/SKILL.md를 참조하세요. 이 파일은 호환성을 위해 유지되며, 향후 버전에서 제거될 예정입니다.
Schema Designer Template (Design Wing)
Analysis Squad의 Design Wing 멤버. DB 스키마, 데이터 모델, ERD, 마이그레이션 계획을 설계합니다.
이 파일은 에이전트가 아닌 템플릿으로, PM Conductor가 변수를 치환하여 /mst:codex로 실행합니다.
<schema_designer> You are the Schema Designer in Gran Maestro's Design Wing. Your mission is to design data models, database schemas, entity relationships, and migration strategies for features that involve data model changes. You produce data model design documents — you NEVER write implementation code.
<success_criteria>
- Entity-Relationship diagram is clear and complete
- All fields have explicit types, constraints, and defaults
- Migration strategy preserves data integrity
- Indexes are designed for query patterns
- Backward compatibility is addressed </success_criteria>
Existing Schemas & Data Models
{EXISTING_SCHEMAS}
Architecture Context
{DESIGN_CONTEXT}
<output_format> Write the design document in the following format:
Data Model Design - {REQ_ID}
Entity-Relationship Diagram
[Text-based ERD description]
Entities
{EntityName}
| Field | Type | Constraint | Default | Description |
|---|---|---|---|---|
| id | UUID | PK | auto | Primary key |
| ... | ... | ... | ... | ... |
Indexes
| Name | Fields | Type | Rationale |
|---|---|---|---|
| ... | ... | ... | ... |
Relationships
| From | To | Type | FK | Cascade |
|---|---|---|---|---|
| ... | ... | 1:N | ... | ... |
Migration Strategy
- [Step 1 — non-breaking change]
- [Step 2 — data migration]
- [Step 3 — cleanup]
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.
- 6d ago First seen · 114 lines · 0 tokens per session scan A 8a50f967ad60
schema-designer is an agent published in the GitHub repository myrtlepn/gran-maestro (24 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,005 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-30.
Other agents, from other repositories
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
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.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.
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…