agentmods.dev

badi: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from fatihkan/badi. Its token cost is not measured, scanned A, original, MIT.

A set of hooks that runs after the agent finishes certain tool calls. It logs file changes after edits and tracks use after shell commands or file changes.

In plain words
What is it for?
Logging edits to files and notebooks, and tracking Bash, writing, and editing activity.
Why use it?
It keeps a record of changes and tool use without requiring the developer to record them manually. The input does not specify the format or destination of those records.

Hook for Claude Code

Written for Claude Code: $CLAUDE_PROJECT_DIR variable. Also seen: names the NotebookEdit tool.

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

Part of the badi plugin — 81 skills, 86 commands, 30 agents, 7 hooks shipped together

One of 8 entries in settings.json — they are configured in one file and arrive together.

not rated 7repo yesterday A scan tokens not measured original MIT
View source ↗ fatihkan/badi npmjs.com
Reuse

Borrowing it

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

Made for: Claude Code.

Or install badi, the plugin that ships this one along with the rest of its 81 skills, 86 commands, 30 agents, 7 hooks.

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 PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/fatihkan/badi/post-tool-use.svg)](https://agentmods.dev/hooks/fatihkan/badi/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/fatihkan/badi/post-tool-use"><img src="https://agentmods.dev/badge/hooks/fatihkan/badi/post-tool-use.svg" alt="Measured on agentmods" 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

PostToolUse 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 today.

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

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit|NotebookEdit",
      "hooks": [
        {
          "type": "command",
          "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/log-changes.mjs\"",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "Bash|Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "node \"$CLAUDE_PROJECT_DIR/.claude/hooks/track-usage.mjs\"",
          "timeout": 3000
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 8. 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. today First seen · 24 lines scan A 00806195ea01

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository fatihkan/badi (7 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-09-06.

Building agentsDebuggingagentsai-workflowclideveloper-toolshooks
Related

Other hooks, from other repositories

SessionStart

Runs when a session starts, executing on-start.js via node. From google-gemini/gemini-cli.

google-gemini/gemini-cli · not measured

PreToolUse

Runs before the agent uses a tool for Bash tool calls, running an inline shell check. From apache/superset.

apache/superset · not measured

PreToolUse

Runs before the agent uses a tool, executing pre-write.sh and pre-bash.sh (2 commands). From anthropics/claude-cookbooks.

anthropics/claude-cookbooks · not measured

PreCompact

Runs before the context is compacted for manual and auto tool calls, executing hook-handler.cjs via node (4 commands). From ruvnet/RuView.

ruvnet/RuView · not measured

SessionStart

Runs when a session starts on startup, clear and compact, executing run-hook.cmd. From obra/superpowers.

obra/superpowers · not measured

SessionStart

Runs when a session starts, running an inline shell check. From Egonex-AI/Understand-Anything.

Egonex-AI/Understand-Anything · not measured