dlt-pipeline-config

dlt-pipeline-config is a cursor rule for Cursor from revodatanl/databricks-mcp-server. It costs 17 tokens per session (469 once invoked), scanned A, original, MIT.

A configuration rule for Databricks Delta Live Tables, a service for building data pipelines with streaming, transformations, and data-quality checks. It describes settings for serverless and cluster-based pipelines.

In plain words
What is it for?
Use it when writing Databricks bundle resources for ETL or streaming pipelines. It covers serverless settings, notebooks, schedules, and traditional cluster definitions.
Why use it?
It prevents invalid or unsuitable pipeline configuration, such as using worker_size with a serverless pipeline.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is path: ../../src/bronze_layer.py.

Good fit Use it when writing Databricks bundle resources for ETL or streaming pipelines. It covers serverless settings, notebooks, schedules, and traditional cluster definitions.

Compare 6 cursor rules from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/revodatanl/databricks-mcp-server
agentmods
npx agentmods add rules/revodatanl/databricks-mcp-server/dlt-pipeline-config

Made for: Cursor.

Wrote 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.

agentmods badge for dlt-pipeline-config

README.md
[![agentmods](https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/dlt-pipeline-config.svg)](https://agentmods.dev/rules/revodatanl/databricks-mcp-server/dlt-pipeline-config)
Your own site
<a href="https://agentmods.dev/rules/revodatanl/databricks-mcp-server/dlt-pipeline-config"><img src="https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/dlt-pipeline-config.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00017 $0.00469
Opus 5 $0.00009 $0.00234
Sonnet 5 $0.00003 $0.00094
Haiku 4.5 $0.00002 $0.00047

Measured 7d ago against content hash 1bca52ec1f95, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

dlt-pipeline-config 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 7d 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.

rules/.cursor/dlt-pipeline-config.mdc · 66 lines

What it actually says

  • Use a DLT Pipeline for declarative ETL, streaming, and data quality enforcement in Databricks.

  • For serverless DLT pipelines, do not use the worker_size key.

  • Example: Basic DLT Pipeline (Serverless)

    resources:
      pipelines:
        data_processing_pipeline:
          name: "${bundle.target}-data-processing-pipeline"
          catalog: main
          target: ${bundle.target}_data
          serverless: true
          libraries:
            - notebook:
                path: ../../src/bronze_layer.py
            - notebook:
                path: ../../src/silver_layer.py
            - notebook:
                path: ../../src/gold_layer.py
          configuration:
            bundle.sourcePath: ${workspace.file_path}/src
            pipeline.trigger.interval: "1 hour"
    
  • For DLT pipelines using traditional clusters, specify clusters under the clusters key:

    resources:
      pipelines:
        streaming_pipeline:
          name: "${bundle.target}-streaming-pipeline"
          catalog: main
          target: ${bundle.target}_streaming
          libraries:
            - notebook:
                path: ../src/streaming_dlt.py
          clusters:
            - label: "default"
              node_type_id: "i3.xlarge"
              num_workers: 2
    
  • Essential pipeline fields:

    • catalog: Unity Catalog name (commonly "main")
    • target: Database/schema for output tables
    • libraries: List of DLT notebooks (must use @dlt.table decorators)
    • configuration: Pipeline settings and parameters
  • DLT notebooks should define tables using the @dlt.table decorator. Example:

    import dl
    @dlt.table
    def raw_data():
        return spark.read.format("json").load("/path/to/data"
    @dlt.table
    def clean_data():
        return dlt.read("raw_data").filter(col("value").isNotNull())
    
  • Always use data quality expectations in DLT pipelines where appropriate.

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. 7d ago First seen · 66 lines · 17 tokens per session scan A 1bca52ec1f95

Subscribe to this mod's changes

dlt-pipeline-config is a cursor rule published in the GitHub repository revodatanl/databricks-mcp-server (7 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 469 once invoked, about $0.0001 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.