claude-code-hooks: Settings file for Claude Code

.claude/settings.json

claude-code-hooks is a settings file for Claude Code from shanraisshan/claude-code-hooks. Its token cost is not measured, scanned A, a copy of claude-code-best-practice, MIT.

Agent settings that connect a Python hook script to events before tools run, during permission requests, after tools run, and after tool failures.

In plain words
What is it for?
Use them to configure hook processing for tool calls, permission prompts, successful tool executions, and failed tool executions.
Why use it?
They provide one place to apply project-specific behavior around tool use and permission handling.

Settings file for Claude Code

Written for Claude Code: ${CLAUDE_PROJECT_DIR} variable.

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

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

Reuse

Borrowing it

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

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 claude-code-hooks

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

Your own site · 80×15
<a href="https://agentmods.dev/settings/shanraisshan/claude-code-hooks/settings"><img src="https://agentmods.dev/badge/settings/shanraisshan/claude-code-hooks/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 95% copy Near-identical to another mod in the catalogue.
Security

Grade A, and why

claude-code-hooks 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 1mo 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.

Origin

This is a copy

95% identical to claude-code-best-practice — 90 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/settings.json · 400 lines

How it starts

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

{
  "disableAllHooks": false,
  "hooks": {
    "PreToolUse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
            "timeout": 5000,
            "async": true,
            "statusMessage": "PreToolUse"
          }
        ]
      }
    ],
    "PermissionRequest": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
            "timeout": 5000,
            "async": true,
            "statusMessage": "PermissionRequest"
          }
        ]
      }
    ],
    "PostToolUse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
            "timeout": 5000,
            "async": true,
            "statusMessage": "PostToolUse"
          }
        ]
      }
    ],
    "PostToolUseFailure": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
            "timeout": 5000,
            "async": true,
            "statusMessage": "PostToolUseFailure"
          }
        ]
      }
    ],
    "PostToolBatch": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
            "timeout": 5000,
            "async": true,
            "statusMessage": "PostToolBatch"
          }
        ]
      }
    ],
    "UserPromptSubmit": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "python3 ${CLAUDE_PROJECT_DIR}/.claude/hooks/scripts/hooks.py",
            "timeout": 5000,
            "async": true,
            "statusMessage": "UserPromptSubmit"
          }
        ]
      }
    ],
    "UserPromptExpansion": [
      

Read the full file on GitHub · 400 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. 1mo ago First seen · 400 lines scan A 590a16a460f4

Subscribe to this mod's changes

claude-code-hooks is a settings file published in the GitHub repository shanraisshan/claude-code-hooks (563 stars, last pushed 4mo ago), licensed MIT. 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. It is 95% identical to claude-code-best-practice, differing in 90 lines, and is treated as a copy.