bluetemberg: Hook for Claude Code

.claude/settings.json

PreToolUse is a hook for Claude Code from prototypdigital/bluetemberg. Its token cost is not measured, scanned A, original, MIT.

A check that runs before the agent enters a worktree, which is a separate working copy of a project, and requires a conventional branch name.

In plain words
What is it for?
Use it to enforce branch names such as feat/my-feature, fix/description, or docs/topic when EnterWorktree is called.
Why use it?
It prevents worktrees from being created with missing or unsuitable branch names.

Hook for Claude Code

Written for Claude Code: PreToolUse hook event. Also seen: positional $N argument.

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

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

Reuse

Borrowing it

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

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/prototypdigital/bluetemberg/pre-tool-use/github.svg)](https://agentmods.dev/hooks/prototypdigital/bluetemberg/pre-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/prototypdigital/bluetemberg/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/prototypdigital/bluetemberg/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/prototypdigital/bluetemberg/pre-tool-use"><img src="https://agentmods.dev/badge/hooks/prototypdigital/bluetemberg/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.
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 yesterday.

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

How it starts

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

{
  "PreToolUse": [
    {
      "matcher": "EnterWorktree",
      "hooks": [
        {
          "type": "command",
          "command": "bash -c 'v=$(jq -rs --arg f \"$1\" '\\''if length == 1 then .[0] else error(\"expected one JSON payload\") end | ($f / \".\") as $p | .tool_input | if type == \"object\" then . else error(\"tool_input is not an object\") end | getpath($p) | if . == null then empty else . end | if type == \"array\" or type == \"object\" then error(\"not a string, number or boolean\") else . end'\\'' 2>/dev/null); if [ \"$?\" -ne 0 ]; then printf \"bluetemberg guardrail: could not read field .%s from the hook payload (is jq installed? It must be one JSON object with an object tool_input, and the field a string, number or boolean), so the condition cannot be evaluated. Blocking.\\n\" \"$1\" >&2; exit 2; fi; fail=; bad=; if [ -n \"$5\" ] && [ -z \"$v\" ]; then fail=1; fi; if [ -n \"$2\" ]; then [[ \"$v\" =~ $2 ]]; s=$?; if [ \"$s\" -eq 2 ]; then bad=1; elif [ \"$s\" -eq 0 ]; then fail=1; fi; fi; if [ -n \"$3\" ]; then [[ \"$v\" =~ $3 ]]; s=$?; if [ \"$s\" -eq 2 ]; then bad=1; elif [ \"$s\" -ne 0 ]; then fail=1; fi; fi; if [ -n \"$bad\" ]; then printf \"bluetemberg guardrail: the condition regex for field .%s is not valid POSIX ERE, so the condition cannot be evaluated. Blocking; fix the guardrail regex.\\n\" \"$1\" >&2; exit 2; fi; if [ -n \"$fail\" ]; then printf \"%s\\n\" \"$4\" >&2; exit 2; fi' bluetemberg 'name' '^claude/' '' 'EnterWorktree requires a conventional branch name. Call EnterWorktree again with name=\"type/description\" (e.g. feat/my-feature). Ask the user what the branch should be called if unclear. Types: feat fix chore refactor docs test' '1'"
        }
      ]
    },
    {
      "hooks": [
        {
          "type": "command",
          "command": "bash -c 'name=$(cat | jq -r \".name // empty\" 2>/dev/null); if [[ -z \"$name\" || \"$name\" == claude/* ]]; then echo \"EnterWorktree requires a conventional branch name. Call EnterWor

Read the full file on GitHub · 22 lines

Same file

What else settings.json configures

This page is one entry in a file that holds 4. 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. yesterday Changed 34b0b4f65265
  2. 7d ago Changed · +9 lines fdd58455dc19
  3. 2mo ago First seen · 13 lines scan A 48a678326d20

Subscribe to this mod's changes

PreToolUse is a hook published in the GitHub repository prototypdigital/bluetemberg (4 stars, last pushed yesterday), licensed MIT. 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-31.

Related

PreToolUse compared with hooks from other repositories

PreToolUse next to 6 hooks from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
PreToolUseprototypdigital/bluetembergHook4yesterdayMITA—Claude Code
PostToolUsesupabase/supabaseHook115kyesterdayApache-2.0A—Claude Code
SessionStartsupabase/supabaseHook115kyesterdayApache-2.0A—Claude Code
SessionStartgoogle-gemini/gemini-cliHook109kyesterdayApache-2.0A—Claude Code
PreToolUseapache/supersetHook75kyesterdayApache-2.0A—Claude Code
PreToolUseanthropics/claude-cookbooksHook54k2d agoMITA—Claude Code
PostToolUseanthropics/claude-plugins-officialHook46kyesterdayApache-2.0A—Claude Code