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 agentmods add rules/revodatanl/databricks-mcp-server/scheduling-production-patternsgit clone --depth 1 https://github.com/revodatanl/databricks-mcp-serverWrote 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/rules/revodatanl/databricks-mcp-server/scheduling-production-patterns)<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="Measured on agentmods" 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 | $0.00021 | $0.00588 |
| Opus 5 | $0.00010 | $0.00294 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
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 3d 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.
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
```
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.
- 3d ago First seen · 93 lines · 21 tokens per session scan A aa36e6604c94
scheduling-production-patterns is a cursor rule published in the GitHub repository revodatanl/databricks-mcp-server (7 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 588 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.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.