What is job-configuration?

A set of guidance for configuring Databricks Jobs, which run scheduled or multi-step data workflows. It covers YAML job definitions, schedules, tasks, dependencies, clusters, and notifications.

Use it to define scheduled jobs, multi-step ETL workflows, notebook tasks, task dependencies, and job clusters in resources/jobs YAML files.

It provides a consistent structure for describing Databricks workflows and reduces mistakes in job configuration.

job-configuration — Cursor rule for Cursor by revodatanl

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/job-configuration

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/job-configuration/github.svg)](https://agentmods.dev/rules/revodatanl/databricks-mcp-server/job-configuration)

Your own site

<a href="https://agentmods.dev/rules/revodatanl/databricks-mcp-server/job-configuration"><img src="https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/job-configuration/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/revodatanl/databricks-mcp-server/job-configuration"><img src="https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/job-configuration.svg" alt="Reviewed on agentmods" width="80" 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 536 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.

Model	Per session	Once invoked
Fable 5.1	$0.00017	$0.00536
Opus 5.5	$0.00007	$0.00214
Sonnet 5.5	$0.00003	$0.00107
Haiku 4.5	$0.00002	$0.00054

Measured 2mo ago against content hash 311f10806a5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

job-configuration 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.

rules/.cursor/job-configuration.mdc · 80 lines

What it actually says

Use a Job to orchestrate scheduled or multi-step workflows in Databricks.

Define jobs in YAML under the resources/jobs/ directory.

Example: Simple Scheduled Job

resources:
  jobs:
    daily_data_job:
      name: "${bundle.target}-daily-data-processing"
      trigger:
        periodic:
          interval: 1
          unit: DAYS
          pause_status: UNPAUSED
      email_notifications:
        on_failure:
          - ${workspace.current_user.userName}
      tasks:
        - task_key: process_data
          job_cluster_key: main_cluster
          notebook_task:
            notebook_path: ../src/process_data.ipynb
            base_parameters:
              environment: ${bundle.target}
      job_clusters:
        - job_cluster_key: main_cluster
          new_cluster:
            spark_version: 15.4.x-scala2.12
            node_type_id: i3.xlarge
            num_workers: 2

Example: Multi-Task Job with Dependencies

resources:
  jobs:
    etl_workflow:
      name: "${bundle.target}-etl-workflow"
      trigger:
        manual: {}
      tasks:
        - task_key: extract
          job_cluster_key: main_cluster
          notebook_task:
            notebook_path: ../src/extract.ipynb
        - task_key: transform
          depends_on:
            - task_key: extract
          job_cluster_key: main_cluster
          notebook_task:
            notebook_path: ../src/transform.ipynb
        - task_key: load
          depends_on:
            - task_key: transform
          job_cluster_key: main_cluster
          notebook_task:
            notebook_path: ../src/load.ipynb
      job_clusters:
        - job_cluster_key: main_cluster
          new_cluster:
            spark_version: 15.4.x-scala2.12
            node_type_id: i3.xlarge
            autoscale:
              min_workers: 1
              max_workers: 4

Essential job fields:
- name: Display name (should include "${bundle.target}-job-name")
- trigger: periodic, manual, or continuous
- tasks: notebook_task, python_wheel_task, pipeline_task, sql_task
- job_clusters: compute resources
- email_notifications: on_success, on_failure

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.

2mo ago First seen · 80 lines · 17 tokens per session scan A 311f10806a5b

Subscribe to this mod's changes

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

DevOps and cloud

job-configuration

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other cursor rules, from other repositories

ponytail

angular-20

dev-standard

prefer-direct-imports-over-module-mocks

control-plane-descriptors

family-instance-domain-actions