OpenMetadata: Hook for Claude Code

.claude/settings.json

PreToolUse is a hook for Claude Code from open-metadata/OpenMetadata. Its token cost is not measured, scanned A, original, Apache-2.0.

A pre-action check that runs before Bash, Edit, and Write commands in OpenMetadata. It blocks skipping Git's pre-commit checks and prevents direct edits to files produced by code generation.

In plain words
What is it for?
Use it to reject Git commands containing --no-verify and prevent edits to generated OpenMetadata UI, ingestion, and build-output files.
Why use it?
It stops changes that could bypass required checks or be overwritten later by the build process.

Hook for Claude Code

Written for Claude Code: ${CLAUDE_PROJECT_DIR variable. Also seen: mentions CLAUDE.md; mentions AGENTS.md.

This is open-metadata/OpenMetadata's own configuration. It tells Claude Code how to work on OpenMetadata 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 OpenMetadata configures →

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

About the project

OpenMetadata is an open platform that organizes information about data, including its meaning, ownership, quality, history, and relationships. It provides governed context for data users, AI assistants, and agents that need to discover and understand trustworthy data.

open-metadata/OpenMetadata · 15,552 stars · on GitHub · open-metadata.org

Reuse

Borrowing it

Nothing to install: this file belongs to open-metadata/OpenMetadata. 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/open-metadata/OpenMetadata/main/.claude/settings.json
Clone the repo
git clone --depth 1 https://github.com/open-metadata/OpenMetadata

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 PreToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/open-metadata/openmetadata/pre-tool-use/github.svg)](https://agentmods.dev/hooks/open-metadata/openmetadata/pre-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/open-metadata/openmetadata/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/open-metadata/openmetadata/pre-tool-use/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 PreToolUse

Your own site · 80×15
<a href="https://agentmods.dev/hooks/open-metadata/openmetadata/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/open-metadata/openmetadata/pre-tool-use.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. ✓ AI security review Fable 5.1 · 7 Sept 2026 📄 Read the review
Origin original No closer match found in the catalogue.
Security

Grade A, and why

PreToolUse 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 13d ago.

A static scan of the commands this hook runs, not an audit. A hook is shell that executes on your machine at the event it names, which is why every command in it is printed with what was found.

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 · 44 lines

How it starts

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

{
  "PreToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "if echo \"$CLAUDE_TOOL_INPUT\" | grep -q -- '--no-verify'; then echo '{\"decision\": \"block\", \"reason\": \"Do not skip pre-commit hooks with --no-verify. Fix the underlying issue instead.\"}'; exit 2; fi",
          "description": "Block --no-verify on git commits"
        },
        {
          "type": "command",
          "command": "bash \"${CLAUDE_PROJECT_DIR:-.}/.github/scripts/java_impact_map_hook.sh\" pre-pr",
          "description": "Block git push / gh pr create while the branch leaves Java code or ITs without an impact-map area"
        }
      ]
    },
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "FILE=$(echo \"$CLAUDE_TOOL_INPUT\" | jq -r '.file_path // empty' 2>/dev/null); if [ -n \"$FILE\" ] && echo \"$FILE\" | grep -qE '(openmetadata-ui/src/main/resources/ui/src/generated/|ingestion(-core)?/src/metadata/generated/|/target/generated-sources/)'; then echo '{\"decision\": \"block\", \"reason\": \"Blocked write to GENERATED output. This file is produced by code generation (jsonschema2pojo / datamodel-code-generator / quicktype / ANTLR); hand edits are overwritten by the next build and, for the committed UI types, reverted by the typescript-type-generation CI job. Edit the JSON Schema under openmetadata-spec/src/main/resources/json/schema/ and run make generate (a repo-root-only target). See .claude/rules/schema-first.md.\"}'; exit 2; fi",
          "description": "Block edits to generated output; direct to the schema + make generate"
        },
        {
          "type": "command",
          "command": "FILE=$(echo \"$CLAUDE_TOOL_INPUT\" | jq -r '.file_path // empty' 2>/dev/null); if [ -n \"$FILE\" ] && echo \"$FILE\" | grep -qE 'docs/generated/(entity-index|api-reference)\\.md'; then echo '{\"decision\": \"block\", \"reason\": \"Blocked write to a GENERAT

Read the full file on GitHub · 44 lines

Same file

What else settings.json configures

This page is one entry in a file that holds 3. 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. 13d ago Changed · +5 lines 5dc60fe7a3fb
  2. 1mo ago First seen · 39 lines scan A eeef0dcf8463

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository open-metadata/OpenMetadata (15,552 stars, last pushed today), licensed Apache-2.0. Its token cost is not measured: a hook is shell that never enters the context. 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.