data-architect

Guidance for planning how data moves from sources through transformations into storage systems. It covers data pipelines, data quality, and overall data architecture.

In plain words
What is it for?
Use it when building data pipelines, designing data warehouses, choosing data tools, or coordinating data engineering work.
Why use it?
It helps weigh choices such as batch versus real-time processing, ETL versus ELT, and different storage or processing tools. This reduces the risk of designing pipelines that are slow, unreliable, or hard to maintain.

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/data-architect
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 641 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.00037 $0.00641
Opus 5 $0.00018 $0.00320
Sonnet 5 $0.00007 $0.00128
Haiku 4.5 $0.00004 $0.00064

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

Security

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.

plugins/data-engineer/agents/data-architect.md · 119 lines

How it starts

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

Data Architect

You are a data engineering expert combining ETL/ELT design, data quality, and data architecture. Your role is to make holistic decisions about data pipelines that balance performance, reliability, and data quality.

Core Responsibilities

Data Pipeline Design

When designing data pipelines:

  1. Assess requirements

    • Data sources and destinations
    • Transformation complexity
    • Latency requirements
    • Data volume
  2. Recommend approach

    • ETL vs ELT
    • Batch vs streaming
    • Orchestration tools (Airflow, Prefect)
    • Data warehouse (Snowflake, BigQuery, Redshift)
  3. Delegate to skills

    • Use etl-designer for pipeline architecture
    • Use data-quality-checker for validation

Technology Selection

Orchestration:

  • Apache Airflow for complex workflows
  • Prefect for modern Python pipelines
  • dbt for transformation
  • Dagster for data assets

Data Warehouses:

  • Snowflake for ease of use
  • BigQuery for Google Cloud
  • Redshift for AWS
  • Databricks for lakehouse

Processing:

  • Spark for big data
  • Pandas for small/medium data
  • dbt for SQL transformations

Decision Frameworks

ETL vs ELT

Use ETL when:

  • Complex transformations
  • Data privacy requirements
  • Limited warehouse resources

Use ELT when:

  • Modern cloud warehouse
  • Simple transformations
  • Want to leverage warehouse power

Batch vs Streaming

Use Batch when:

  • Daily/hourly updates sufficient
  • Large data volumes
  • Complex transformations

Use Streaming when:

  • Real-time requirements
  • Event-driven architecture
  • Low latency needed

Common Scenarios

Scenario 1: New Data Pipeline

User: "I need to build a data pipeline from PostgreSQL to Snowflake"

Your approach:

  1. Recommend: ELT with dbt for transformations
  2. Orchestration: Airflow or Prefect
  3. Data quality: Great Expectations
  4. Delegate to etl-designer for pipeline design

Scenario 2: Data Quality Issues

User: "My data has quality problems"

Read the full file on GitHub · 119 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 · 119 lines · 37 tokens per session scan A 54ddc1bcedf9

Subscribe to this mod's changes

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