init-databricks-ml

init-databricks-ml is a skill for Claude Code, Codex from duonginspace/claude-code-databricks-ml. It costs 46 tokens per session (5,613 once invoked), scanned C, original, MIT.

A project setup workflow for Databricks machine-learning work, using MLflow to track experiments and Claude Code to assist with the project.

In plain words
What is it for?
Use it when starting a Databricks ML project or adding Databricks support to an existing one. It helps prepare ignore files and folders for code, data, research results, MLflow output, and development environments.
Why use it?
It fills in missing project files and settings while checking existing files first, so setup changes do not unnecessarily replace work already there.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/duonginspace/claude-code-databricks-ml/init-databricks-ml
Any agent
npx skills add duonginspace/claude-code-databricks-ml --skill init-databricks-ml
Clone the repo
git clone --depth 1 https://github.com/duonginspace/claude-code-databricks-ml

Made for: Claude Code, Codex.

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 init-databricks-ml

README.md
[![agentmods](https://agentmods.dev/badge/skills/duonginspace/claude-code-databricks-ml/init-databricks-ml.svg)](https://agentmods.dev/skills/duonginspace/claude-code-databricks-ml/init-databricks-ml)
Your own site
<a href="https://agentmods.dev/skills/duonginspace/claude-code-databricks-ml/init-databricks-ml"><img src="https://agentmods.dev/badge/skills/duonginspace/claude-code-databricks-ml/init-databricks-ml.svg" alt="Measured on agentmods" height="20"></a>
Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,613 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. Scan, not verified.
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 $0.00046 $0.05613
Opus 5 $0.00023 $0.02806
Sonnet 5 $0.00009 $0.01123
Haiku 4.5 $0.00005 $0.00561

Measured 4d ago against content hash 78629c45d07c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

init-databricks-ml scanned grade C with 2 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 4d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

"Bash(rm -rf *)",

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

subprocess.check_call(
skills/init-databricks-ml/SKILL.md · 591 lines

How it starts

The opening of the file, as written. The whole thing — 591 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Initialize / Update Databricks ML Project

Set up or update the current project with Databricks + MLflow + Claude Code integration. For each item below, CHECK if it already exists before creating. If it exists, skip it or merge missing parts. Only create/update what is missing.

Checklist

1. .gitignore

Check if .gitignore exists. If missing, create it with:

# Python-generated files
__pycache__/
*.py[oc]
*.py[cod]
build/
dist/
wheels/
*.egg-info
*.whl

# Virtual environments
.venv/
venv/

# Environment
.env*
!.env.example

# MLflow
mlflow_results/

# EDA / Research
eda_results/
research/

# OS
.DS_Store

# Claude
.claude/

# uv
uv.lock

# misc
std.out

If it exists, check that .env*, !.env.example, mlflow_results/, .venv/, eda_results/, research/, .claude/, uv.lock, and std.out are listed. Append missing entries.

1b. .claudeignore

Check if .claudeignore exists. If missing, create it. This file prevents Claude Code from indexing large data files, model artifacts, and binary files that are irrelevant to code understanding.

# Data files — large binary/tabular data that Claude doesn't need to read
*.csv
*.tsv
*.parquet
*.feather
*.arrow
*.h5
*.hdf5
*.pkl
*.pickle
*.npy
*.npz
*.zarr
*.tfrecord
*.avro
*.orc

# Data directories
data/
datasets/

# Model artifacts
*.pt
*.pth
*.onnx
*.safetensors
*.bin
*.ckpt
models/

# Images / media
*.png
*.jpg
*.jpeg
*.gif
*.bmp
*.svg
*.mp4
*.mp3
*.wav

# Archives
*.zip
*.tar
*.tar.gz
*.tgz
*.gz
*.bz2
*.7z
*.rar

# Virtual environments
.venv/
venv/

# Build artifacts
build/
dist/
wheels/
*.egg-info/
*.whl

# MLflow local results
mlflow_results/

# EDA / Research outputs
eda_results/
research/

# Misc
__pycache__/
*.pyc
.DS_Store
std.out
uv.lock

If it exists, check that the data file extensions (*.csv, *.parquet, *.h5, *.pkl, *.npy), data directories (data/, datasets/), model artifact extensions (*.pt, *.pth, *.onnx, *.safetensors), and build/output directories (mlflow_results/, eda_results/, research/) are listed. Append missing entries.

Read the full file on GitHub · 591 lines

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. 4d ago First seen · 591 lines · 46 tokens per session scan C 78629c45d07c

Subscribe to this mod's changes

init-databricks-ml is a skill published in the GitHub repository duonginspace/claude-code-databricks-ml (5 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 5,613 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens