zenml: Settings file for Claude Code

.claude/settings.json

zenml is a settings file for Claude Code from zenml-io/zenml. Its token cost is not measured, scanned A, original, Apache-2.0.

A Claude Code settings file with a pre-tool check for Bash commands. Before a Git commit, it runs the project’s formatting script and blocks the commit if formatting fails.

In plain words
What is it for?
Automatically formatting code before Git commits and enforcing that formatting succeeds before the commit command continues.
Why use it?
It prevents commits from proceeding when the configured formatter reports an error.

Settings file for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable.

This is zenml-io/zenml's own configuration. It tells Claude Code how to work on zenml itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zenml configures →

One of 2 entries in settings.json upstream. Installing this one merges just its entry into your config; the other 1 are separate, each on its own page.

About the project

ZenML is a Python framework for turning machine-learning and AI workflows into tracked pipelines that run on different infrastructure backends. It is for ML and AI engineers building applications such as model-training workflows, language-model systems, and agent loops in company environments.

zenml-io/zenml · 5,629 stars · on GitHub · zenml.io

Reuse

Borrowing it

Nothing to install: this file belongs to zenml-io/zenml. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/zenml-io/zenml/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/zenml-io/zenml

Made for: Claude Code.

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 zenml

README.md
[![agentmods](https://agentmods.dev/badge/settings/zenml-io/zenml/settings/github.svg)](https://agentmods.dev/settings/zenml-io/zenml/settings)
Your own site
<a href="https://agentmods.dev/settings/zenml-io/zenml/settings"><img src="https://agentmods.dev/badge/settings/zenml-io/zenml/settings/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 zenml

Your own site · 80×15
<a href="https://agentmods.dev/settings/zenml-io/zenml/settings"><img src="https://agentmods.dev/badge/settings/zenml-io/zenml/settings.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
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.
Security

Grade A, and why

zenml 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 14d 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.

.claude/settings.json · 18 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-settings.json",
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [
          {
            "type": "command",
            "command": "if jq -r '.tool_input.command' 2>/dev/null | grep -q 'git commit'; then echo '🔍 Running pre-commit formatting...'; bash \"$CLAUDE_PROJECT_DIR\"/scripts/format.sh && echo '✅ Formatting complete' || { echo '❌ Formatting failed - commit blocked' >&2; exit 2; }; fi",
            "timeout": 300
          }
        ]
      }
    ]
  }
}
Same file

What else settings.json configures

This page is one entry in a file that holds 2. Installing the file brings all of them; each is measured and scanned on its own page.

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. 14d ago Changed ab389ca62852
  2. 2mo ago First seen · 18 lines scan A 34456e365049

Subscribe to this mod's changes

zenml is a settings file published in the GitHub repository zenml-io/zenml (5,629 stars, last pushed yesterday), licensed Apache-2.0. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-30.