claude-devtools: Hook for Claude Code

.claude/settings.json

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

An after-edit check that runs when the agent finishes editing, writing, or changing a notebook. It formats JavaScript, TypeScript, JSON, and CSS files and fixes some JavaScript or TypeScript lint issues.

In plain words
What is it for?
It is for automatically running ESLint and Prettier on changed project files after Edit, Write, or NotebookEdit actions.
Why use it?
It removes the need to run these formatting and lint commands manually after every change. This helps keep edited files consistent, although failed checks are ignored.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event. Also seen: names the NotebookEdit tool.

This is matt1398/claude-devtools's own configuration. It tells Claude Code how to work on claude-devtools 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-devtools 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.

About the project

claude-devtools is a visual debugging application that reads Claude Code's locally saved logs and session transcripts and presents their hidden details. Developers use it to inspect tool inputs and outputs, file activity, token usage, subagents, context consumption, and team coordination. The catalogue entries add commands, hooks, agents, instructions, and settings for the tool.

matt1398/claude-devtools · 3,994 stars · on GitHub · claude-dev.tools

Reuse

Borrowing it

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

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 PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/matt1398/claude-devtools/post-tool-use/github.svg)](https://agentmods.dev/hooks/matt1398/claude-devtools/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/matt1398/claude-devtools/post-tool-use"><img src="https://agentmods.dev/badge/hooks/matt1398/claude-devtools/post-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 PostToolUse

Your own site · 80×15
<a href="https://agentmods.dev/hooks/matt1398/claude-devtools/post-tool-use"><img src="https://agentmods.dev/badge/hooks/matt1398/claude-devtools/post-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

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 1mo 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 · 14 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write|NotebookEdit",
      "hooks": [
        {
          "type": "command",
          "command": "jq -r '.tool_input.file_path // .tool_input.notebook_path // empty' | { read file_path; if [ -n \"$file_path\" ] && echo \"$file_path\" | grep -qE '\\.(ts|tsx|js|jsx)$'; then pnpm eslint --fix \"$file_path\" 2>/dev/null || true; fi; if [ -n \"$file_path\" ] && echo \"$file_path\" | grep -qE '\\.(ts|tsx|js|jsx|json|css)$'; then pnpm prettier --write \"$file_path\" 2>/dev/null || true; fi; }",
          "timeout": 30
        }
      ]
    }
  ]
}
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. 1mo ago First seen · 14 lines scan A b9c710e4d2e0

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository matt1398/claude-devtools (3,994 stars, last pushed 1mo 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-08-30.