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 skills add ancoleman/ai-design-components --skill ai-data-engineeringgit clone --depth 1 https://github.com/ancoleman/ai-design-componentsWrote 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/skills/ancoleman/ai-design-components/ai-data-engineering)<a href="https://agentmods.dev/skills/ancoleman/ai-design-components/ai-data-engineering"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/ai-data-engineering/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/skills/ancoleman/ai-design-components/ai-data-engineering"><img src="https://agentmods.dev/badge/skills/ancoleman/ai-design-components/ai-data-engineering.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.00086 | $0.03285 |
| Opus 5.5 | $0.00034 | $0.01314 |
| Sonnet 5.5 | $0.00017 | $0.00657 |
| Haiku 4.5 | $0.00009 | $0.00329 |
Grade A, and why
ai-data-engineering 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 2mo 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 — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI Data Engineering
Purpose
Build data infrastructure for AI/ML systems including RAG pipelines, feature stores, and embedding generation. Provides architecture patterns, orchestration workflows, and evaluation metrics for production AI applications.
When to Use
Use this skill when:
- Building RAG (Retrieval-Augmented Generation) pipelines
- Implementing semantic search or vector databases
- Setting up ML feature stores for real-time serving
- Creating embedding generation pipelines
- Evaluating RAG quality with RAGAS metrics
- Orchestrating data workflows for AI systems
- Integrating with frontend skills (ai-chat, search-filter)
Skip this skill if:
- Building traditional CRUD applications (use databases-relational)
- Simple key-value storage (use databases-nosql)
- No AI/ML components in the application
RAG Pipeline Architecture
RAG pipelines have 5 distinct stages. Understanding this architecture is critical for production implementations.
┌─────────────────────────────────────────────────────────────┐
│ RAG Pipeline (5 Stages) │
├─────────────────────────────────────────────────────────────┤
│ │
│ 1. INGESTION → Load documents (PDF, DOCX, Markdown) │
│ 2. INDEXING → Chunk (512 tokens) + Embed + Store │
│ 3. RETRIEVAL → Query embedding + Vector search + Filters │
│ 4. GENERATION → Context injection + LLM streaming │
│ 5. EVALUATION → RAGAS metrics (faithfulness, relevancy) │
│ │
└─────────────────────────────────────────────────────────────┘
For complete RAG architecture with implementation patterns, see:
references/rag-architecture.md- Detailed 5-stage breakdownexamples/langchain-rag/basic_rag.py- Working implementation
Chunking Strategies
Chunking is the most critical decision for RAG quality. Poor chunking breaks retrieval.
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- examples/dagster-pipelines/embedding_pipeline.py 14 KB runs code
- examples/feast-features/README.md 1010 B
- examples/feast-features/requirements.txt 220 B
- examples/feast-features/setup_features.py 7.8 KB runs code
- examples/langchain-rag/basic_rag.py 7.4 KB runs code
- examples/langchain-rag/hybrid_search.py 9.9 KB runs code
- examples/langchain-rag/main.py 6.8 KB runs code
- examples/langchain-rag/README.md 2.8 KB
- examples/langchain-rag/requirements.txt 321 B
- examples/langchain-rag/streaming_rag.py 11 KB runs code
- examples/llamaindex-agents/query_engine.py 4.2 KB runs code
- examples/llamaindex-agents/README.md 971 B
- examples/llamaindex-agents/requirements.txt 342 B
- outputs.yaml 14 KB
- references/chunking-strategies.md 11 KB
- references/data-versioning.md 7.4 KB
- references/embedding-strategies.md 15 KB
- references/evaluation-metrics.md 18 KB
- references/feature-stores.md 17 KB
- references/langchain-patterns.md 18 KB
- references/orchestration-tools.md 10 KB
- references/rag-architecture.md 15 KB
- scripts/benchmark_retrieval.py 6.7 KB runs code
- scripts/chunk_documents.py 4.7 KB runs code
- scripts/evaluate_rag.py 4.5 KB runs code
- scripts/setup_qdrant.py 5.8 KB runs code
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.
- 2mo ago First seen · 433 lines · 86 tokens per session scan A 3d7278a63802
ai-data-engineering is a skill published in the GitHub repository ancoleman/ai-design-components (526 stars, last pushed 10mo ago), licensed MIT. It adds 86 tokens to every session and 3,285 once invoked, about $0.0003 per session on Opus 5.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.
Other skills, from other repositories
langchain-development
Expert guidance for LangChain and LangGraph development with Python, covering chain composition, agents, memory, and RAG implementations.
ai-product
Every product will be AI-powered. The question is whether you'll build it right or ship a demo that falls apart in production.
ai-pipeline-orchestration
Orchestrate AI/ML pipelines for data ingestion, model training, batch inference, and RAG indexing using Prefect, Airflow, or Dagster.
ai-engineering-toolkit
6 production-ready AI engineering workflows: prompt evaluation (8-dimension scoring), context budget planning, RAG pipeline design, agent security audit (65-point checklist), eval harness building, and product sense coaching.
ai-ml
AI and machine learning workflow covering LLM application development, RAG implementation, agent architecture, ML pipelines, and AI-powered features.
langchain
Apply when building LangChain pipelines, LCEL chains, agents, or retrieval-augmented generation systems.