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 | $0.00061 | $0.01966 |
| Sonnet 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 12d 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.
- 12d 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 1mo ago), licensed MIT. It adds 122 tokens to every session and 3,933 once invoked, about $0.0006 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-31.
Other skills, from other repositories
cloud-deploy-gate
The pre-deployment gate for managed AI platforms (Azure AI Foundry, Google Vertex AI, AWS Bedrock), evals packed, budget set, guardrails on, owner named. Use before any cloud deployment.
context-budget-audit
Audit the seven claimants on an LLM call's context window, set a working ceiling, and cut in the right order. Use when prompts grow, agents drift, or token bills surprise you.
error-analysis-50
Read 50 real failures by hand, cluster them into classes, fix the largest class, and extend the golden set. Use whenever an AI system's score stalls or its failures are 'mysterious'.
eval-first-development
Build the golden set and the automated scorer before touching the prompt, model, or pipeline. Use whenever an AI output's quality will need to be measured, extraction, RAG, agents, classification.
fine-tune-readiness
Decide whether fine-tuning is justified versus prompting or RAG, and gate the training dataset before any LoRA/SFT/DPO run. Use when someone says 'let's fine-tune'.
local-model-fit
Compute the VRAM/RAM budget and pick a model size and quantization before downloading anything. Use when choosing local models, planning GPU hardware, or hitting out-of-memory errors.