scheduling-production-patterns

scheduling-production-patterns is a cursor rule for Cursor from revodatanl/databricks-mcp-server. It costs 21 tokens per session (588 once invoked), scanned A, original, MIT.

A set of patterns for scheduling and operating Databricks jobs and data pipelines. Databricks is a platform for running data-processing work.

In plain words
What is it for?
It helps configure daily or hourly schedules, email alerts, retry behavior, concurrency limits, and jobs that start data pipelines.
Why use it?
It provides consistent examples for timed or manual runs, notifications, retries, time limits, and preventing overlapping runs.

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/dlt_processing.ipynb.

Good fit It helps configure daily or hourly schedules, email alerts, retry behavior, concurrency limits, and jobs that start data pipelines.

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/scheduling-production-patterns

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 scheduling-production-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns/github.svg)](https://agentmods.dev/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns)
Your own site
<a href="https://agentmods.dev/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns"><img src="https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns/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.

agentmods 80×15 button for scheduling-production-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns"><img src="https://agentmods.dev/badge/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 588 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.00021 $0.00588
Opus 5.5 $0.00008 $0.00235
Sonnet 5.5 $0.00004 $0.00118
Haiku 4.5 $0.00002 $0.00059

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

Security

Grade A, and why

scheduling-production-patterns 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/scheduling-production-patterns.mdc · 93 lines

What it actually says

* Use the following patterns for scheduling, notifications, retries, and production integration in Databricks Jobs and Pipelines.

* **Scheduling Options:**
  - Daily at 9 AM:
    ```yaml
    trigger:
      periodic:
        interval: 1
        unit: DAYS
      schedule:
        quartz_cron_expression: "0 0 9 * * ?"
        timezone_id: "America/New_York"
    ```
  - Hourly:
    ```yaml
    trigger:
      periodic:
        interval: 1
        unit: HOURS
    ```
  - Manual (on demand):
    ```yaml
    trigger:
      manual: {}
    ```

* **Notifications and Retries:**
  - Configure email notifications for job events and set retry logic:
    ```yaml
    email_notifications:
      on_start:
        - [email protected]
      on_success:
        - [email protected]
      on_failure:
        - ${workspace.current_user.userName}

    timeout_seconds: 3600  # 1 hour
    max_concurrent_runs: 1

    tasks:
      - task_key: main_task
        retry_on_timeout: true
        max_retries: 2
    ```

* **Job and Pipeline Integration:**
  - To orchestrate a pipeline from a job, use the following pattern:
    ```yaml
    resources:
      pipelines:
        data_pipeline:
          name: "${bundle.target}-data-pipeline"
          catalog: main
          target: ${bundle.target}_processed
          libraries:
            - notebook:
                path: ../src/dlt_processing.ipynb

      jobs:
        orchestration_job:
          name: "${bundle.target}-orchestration"
          tasks:
            - task_key: prepare
              notebook_task:
                notebook_path: ../src/prepare.ipynb

            - task_key: run_pipeline
              depends_on:
                - task_key: prepare
              pipeline_task:
                pipeline_id: ${resources.pipelines.data_pipeline.id}
    ```

* **Common Cron Expressions:**
  - `"0 0 9 * * ?"` — Daily at 9 AM
  - `"0 0 */6 * * ?"` — Every 6 hours
  - `"0 0 9 * * MON"` — Mondays at 9 AM
  - `"0 */15 * * * ?"` — Every 15 minutes

* **Validation Commands:**
  - Use these commands to validate and deploy your bundle:
    ```bash
    databricks bundle validate
    databricks bundle deploy --target dev
    databricks bundle run job_name --target dev
    ```
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. 2mo ago First seen · 93 lines · 21 tokens per session scan A aa36e6604c94

Subscribe to this mod's changes

scheduling-production-patterns is a cursor rule published in the GitHub repository revodatanl/databricks-mcp-server (7 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 588 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.