PostToolUse

A set of automatic checks that run after writing, editing, or using shell commands in a coding project. These checks include code formatting and reminders about Git state and merged changes.

In plain words
What is it for?
Use it to run lint fixes on TypeScript files and check for merge reminders, tracked-file changes, or Git working-directory races after tool actions.
Why use it?
It catches some follow-up work after files change and warns when the main Git working tree may be dirty or affected by a directory mismatch. This reduces overlooked cleanup and repository-state problems.

Hook for Claude Code

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add hooks/go-to-k/cdkd/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/go-to-k/cdkd

Made for: Claude Code.

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. Scan, not verified.
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 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 · 38 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "jq -r '.tool_input.file_path // .tool_response.filePath' | { read -r f; echo \"$f\" | grep -qE '\\.(ts|tsx)$' && vp run lint:fix; } 2>/dev/null || true",
          "timeout": 30,
          "statusMessage": "Running lint:fix..."
        }
      ]
    },
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/post-merge-sync-reminder.sh",
          "timeout": 5,
          "statusMessage": "Post-merge sync reminder check"
        },
        {
          "type": "command",
          "command": "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/main-tree-dirty-detector.sh",
          "timeout": 10,
          "statusMessage": "Checking main-tree tracked-file dirtiness..."
        },
        {
          "type": "command",
          "command": "${CLAUDE_PROJECT_DIR:-.}/.claude/hooks/main-tree-git-cwd-detector.sh",
          "timeout": 10,
          "statusMessage": "Checking for main-tree git cwd-race..."
        }
      ]
    }
  ]
}
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 First seen · 38 lines scan A 143e520d33a7

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository go-to-k/cdkd (122 stars, last pushed yesterday), 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.