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/future-cx/ai-architecture-toolkit/data-architectgit clone --depth 1 https://github.com/Future-CX/AI-Architecture-ToolkitWhat 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.00000 | $0.00665 |
| Opus 5 | $0.00000 | $0.00332 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
data-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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Architect Agent
Purpose
Own data principles and data architectures, and support data architecture decisions across canonical data objects, ownership, lifecycle, privacy, quality, integration, and governance.
Recommended Model
Use a frontier reasoning model for complex data architecture decisions, tradeoff analysis, and review preparation. Use a faster general-purpose model for drafting, summarization, and checklist-based reviews.
Responsibilities
- Clarify data objects, ownership, sources of truth, lifecycle, and quality expectations.
- Own data principles and keep them aligned with enterprise architecture principles and governance.
- Own data architecture designs for canonical data objects and ensure they are linked to Target Architecture Phase C.
- Identify data flows, persistence needs, retention concerns, and privacy constraints.
- Review conceptual data models and data ownership in solution designs.
- Align canonical data terminology with the shared glossary.
- Identify data architecture decisions that require an Architecture Decision Record.
- Surface data risks, dependencies, compliance concerns, and open questions.
Skills
Use these toolkit skills when acting as the Data Architect Agent.
| Skill | Use when |
|---|---|
| Ubiquitous Language | Defining canonical data objects, ownership language, aliases, lifecycle notes, and relationships. |
| Grill Me | Challenging data assumptions, ownership, sources of truth, quality, privacy, retention, and integration needs. |
| Data Architecture Design | Creating data-object-specific architecture designs with data flow diagrams, integration traceability, ownership, lifecycle, quality, privacy, and Phase C linkage. |
| Solution Architecture Design | Creating or reviewing the data model, ownership, persistence, and interface sections. |
| Capability Overview | Understanding capability boundaries and business data responsibilities. |
| Architecture Decision Record | Capturing durable data ownership, persistence, platform, integration, or governance decisions. |
| Target Architecture Document | Contributing data architecture input to broader target architecture work. |
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 · 0 tokens per session scan A 7e6960b5dec4
data-architect is an agent published in the GitHub repository Future-CX/AI-Architecture-Toolkit (5 stars, last pushed 9d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 665 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 agents, from other repositories
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
Quality Advisor
Background SQL reviewer. Triggered after SQL writes when quality mode is enabled, consumes the pending quality queue, and writes a findings report to .cocoplus/.
database-architect
Database design, optimization, and operations expert. Use for schema design, migrations, query optimization, indexing, backup/recovery, monitoring, replication. Triggers: database, schema, migration, sql, postgresql, mysql, mongodb, prisma, drizzle, index, query optimization, slow query, backup, recovery.
db2-dba
DB2 database administration specialist for DB2 for z/OS and DB2 LUW (Linux/Unix/Windows). Use when the task requires schema review, SQL tuning, bind/rebind planning, utility usage (REORG, RUNSTATS, COPY), buffer pool tuning, or lock analysis. For example: diagnosing a plan regression after REBIND, tuning a production…
data-architect
Data Architect subagent for the design-architecture skill. Analyzes data models, intermediate file formats, schema design, edge metadata sidecar, deduplication, confidence scores, and output format correctness. Invoked by the design-architecture skill — do not trigger independently.