PostToolUse

PostToolUse is a hook for Claude Code from TheBeardedBearSAS/claude-craft. Its token cost is not measured, scanned A, original, MIT.

A post-tool hook that runs checks after an agent uses tools such as Edit, Bash, Grep, Glob, or Read. It can format certain edited files and flag unusually large command output.

In plain words
What is it for?
Use it to run the configured post-action script, format supported JavaScript, TypeScript, JSON, and Markdown files, and flag output over the configured size limit.
Why use it?
It keeps generated code formatting consistent and warns when tool output may be too large to handle comfortably.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: reads .claude/ paths.

Part of the claude-craft plugin — 56 skills, 94 commands, 47 agents, 5 hooks shipped together

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

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/thebeardedbearsas/claude-craft/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craft

Made for: Claude Code.

Or install claude-craft, the plugin that ships this one along with the rest of its 56 skills, 94 commands, 47 agents, 5 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/thebeardedbearsas/claude-craft/post-tool-use.svg)](https://agentmods.dev/hooks/thebeardedbearsas/claude-craft/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/thebeardedbearsas/claude-craft/post-tool-use"><img src="https://agentmods.dev/badge/hooks/thebeardedbearsas/claude-craft/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. 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 2d 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 · 53 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit",
      "hooks": [
        {
          "type": "command",
          "command": "FILEPATH=$(jq -r '.tool_input.file_path // empty'); if echo \"$FILEPATH\" | grep -qE '\\.(js|ts|jsx|tsx|json|md|mjs|cjs)$'; then npx prettier --write \"$FILEPATH\" 2>/dev/null || true; fi; exit 0"
        }
      ]
    },
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "~/.claude/hooks/post-tool-filter.sh",
          "timeout": 5000
        }
      ]
    },
    {
      "matcher": "Grep",
      "hooks": [
        {
          "type": "command",
          "command": "OUTPUT_SIZE=$(jq -r '.tool_response.stdout? // .tool_response? // .tool_result? // empty' | wc -c); if [ \"$OUTPUT_SIZE\" -gt 50000 ]; then echo 'NOTICE: Large output (>50KB). Summarize key findings in under 20 lines.'; fi; exit 0",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "Glob",
      "hooks": [
        {
          "type": "command",
          "command": "OUTPUT_SIZE=$(jq -r '.tool_response.stdout? // .tool_response? // .tool_result? // empty' | wc -c); if [ \"$OUTPUT_SIZE\" -gt 50000 ]; then echo 'NOTICE: Large output (>50KB). Focus on the most relevant matches.'; fi; exit 0",
          "timeout": 3000
        }
      ]
    },
    {
      "matcher": "Read",
      "hooks": [
        {
          "type": "command",
          "command": "OUTPUT_SIZE=$(jq -r '.tool_response.stdout? // .tool_response? // .tool_result? // empty' | wc -c); if [ \"$OUTPUT_SIZE\" -gt 51200 ]; then echo 'NOTICE: Large file read (>50KB). Extract only the relevant sections rather than processing the full file.'; fi; exit 0",
          "timeout": 3000
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 6. 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. 2d ago First seen · 53 lines scan A 8e8f558573df

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 3d ago), 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-03.