claude-code-log: Hook for Claude Code

.claude/settings.json

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

A hook that runs after files are written or edited and formats Python code with Ruff, a Python linting and formatting tool.

In plain words
What is it for?
Use it after Write, Edit, or MultiEdit operations when the project uses the shown hook configuration.
Why use it?
It keeps changed Python files formatted automatically after supported editing actions.

Hook for Claude Code

Written for Claude Code: PostToolUse hook event.

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

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

About the project

claude-code-log is a Python command-line tool that turns Claude Code transcript files into readable HTML or Markdown logs. It helps people browse individual sessions or complete project archives, with options for interactive browsing and live updates. The catalogue add-ons extend its use as an agent-related workflow.

daaain/claude-code-log · 1,255 stars · on GitHub · daaain.github.io

Reuse

Borrowing it

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

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/daaain/claude-code-log/post-tool-use/github.svg)](https://agentmods.dev/hooks/daaain/claude-code-log/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/daaain/claude-code-log/post-tool-use"><img src="https://agentmods.dev/badge/hooks/daaain/claude-code-log/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/daaain/claude-code-log/post-tool-use"><img src="https://agentmods.dev/badge/hooks/daaain/claude-code-log/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 2mo 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 · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "uv run ruff format"
        }
      ]
    }
  ]
}
Same file

What else settings.json configures

This page is one entry in a file that holds 2. 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. 2mo ago First seen · 13 lines scan A 21846b8f37bf

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository daaain/claude-code-log (1,255 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-08-30.

Related

PostToolUse compared with hooks from other repositories

PostToolUse next to 6 hooks from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
PostToolUsedaaain/claude-code-logHook1.3kyesterdayMITA—Claude Code
PostToolUsesupabase/supabaseHook115kyesterdayApache-2.0A—Claude Code
SessionStartsupabase/supabaseHook115kyesterdayApache-2.0A—Claude Code
SessionStartgoogle-gemini/gemini-cliHook109kyesterdayApache-2.0A—Claude Code
PreToolUseapache/supersetHook75ktodayApache-2.0A—Claude Code
PreToolUseanthropics/claude-cookbooksHook54k2d agoMITA—Claude Code
PostToolUseanthropics/claude-plugins-officialHook46kyesterdayApache-2.0A—Claude Code