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 mexmarv/ai-genie-factory --skill dlt-pipelinegit clone --depth 1 https://github.com/mexmarv/ai-genie-factoryWrote 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/mexmarv/ai-genie-factory/dlt-pipeline)<a href="https://agentmods.dev/skills/mexmarv/ai-genie-factory/dlt-pipeline"><img src="https://agentmods.dev/badge/skills/mexmarv/ai-genie-factory/dlt-pipeline/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/mexmarv/ai-genie-factory/dlt-pipeline"><img src="https://agentmods.dev/badge/skills/mexmarv/ai-genie-factory/dlt-pipeline.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.00122 | $0.03933 |
| Opus 5.5 | $0.00049 | $0.01573 |
| Sonnet 5.5 | $0.00024 | $0.00787 |
| Haiku 4.5 | $0.00012 | $0.00393 |
Grade A, and why
dlt-pipeline 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 — 484 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DLT Pipeline Patterns — Alpura Medallion Architecture
Apply to every DLT pipeline notebook. Pipelines always flow Bronze → Silver → Gold. Never skip Silver. Never write business logic in Bronze.
Rules
- Bronze: raw ingestion via Auto Loader — no transformations, no filtering
- Silver: validated, deduped, cleaned —
@dlt.expect_or_dropon every quality dimension - Gold: aggregated, app-ready, business-metric-named —
@dlt.materialized_viewpreferred - Never skip Silver — no Bronze → Gold directly
- Always use Databricks Volumes (
/Volumes/catalog/schema/path) — neverdbfs:/ - Use
dlt.read()/dlt.read_stream()— neverspark.read()inside DLT - Name tables:
bronze_<source>,silver_<entity>,gold_<metric> - Log ingestion count and key metrics at every layer — use
_logger.py - All pipeline code runs in DLT notebooks — never in regular notebooks
- Schema evolution: use
cloudFiles.schemaEvolutionMode = "rescue"at Bronze
Bronze — Auto Loader Ingestion
JSON / CSV from Volumes
import dlt
from pyspark.sql import functions as F
from _logger import get_logger
logger = get_logger(__name__)
@dlt.table(
name="bronze_sales_orders",
comment="Raw sales orders — Auto Loader ingestion from Volumes landing zone",
table_properties={"quality": "bronze", "pipelines.reset.allowed": "true"},
)
def bronze_sales_orders():
logger.info("Ingesting bronze_sales_orders")
return (
spark.readStream.format("cloudFiles")
.option("cloudFiles.format", "json")
.option("cloudFiles.schemaLocation", "/Volumes/prod/raw/checkpoints/sales_orders_schema")
.option("cloudFiles.schemaEvolutionMode", "rescue") # new columns → _rescued_data
.option("cloudFiles.inferColumnTypes", "true")
.load("/Volumes/prod/raw/landing/sales_orders/")
.withColumn("_ingested_at", F.current_timestamp())
.withColumn("_source_file", F.input_file_name())
)
Parquet / Delta from Volumes
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 · 484 lines · 122 tokens per session scan A 74de2392bfda
dlt-pipeline is a skill published in the GitHub repository mexmarv/ai-genie-factory (5 stars, last pushed 2mo ago), licensed MIT. It adds 122 tokens to every session and 3,933 once invoked, about $0.0005 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-31.
dlt-pipeline compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dlt-pipelinemexmarv/ai-genie-factory | Skill | 5 | 2mo ago | MIT | A | 122 | Claude Code, Codex |
| databricks-expertpersonamanagmentlayer/pcl | Skill | 44 | 12d ago | Apache-2.0 | A | 74 | Claude Code |
| sql-diagramandre-salvati/databricks-template | Skill | 87 | 1mo ago | Apache-2.0 | A | 121 | Claude Code |
| data-divergenceandre-salvati/databricks-template | Skill | 87 | 1mo ago | Apache-2.0 | A | 123 | Claude Code |
| project-costsandre-salvati/databricks-template | Skill | 87 | 1mo ago | Apache-2.0 | A | 93 | Claude Code |
| cloud-deploy-gatezorost/AI-Engineering-Lab | Skill | 315 | 2mo ago | MIT | A | 49 | Claude Code, Codex |
| error-analysis-50zorost/AI-Engineering-Lab | Skill | 315 | 2mo ago | MIT | A | 46 | Claude Code, Codex |