Use it to run Ruff formatting and automatic fixes on Python files after they are written or edited.

It keeps changed Python files formatted and checked without requiring a separate manual command.

How jesse-smith/searchloinc configures Claude Code

searchloinc: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from jesse-smith/searchloinc. Its token cost is not measured, scanned A, original, MIT.

A hook that runs automatically after Write or Edit tool calls finish. A hook is an automated action triggered by another action.

In plain words

What is it for?: Use it to run Ruff formatting and automatic fixes on Python files after they are written or edited.
Why use it?: It keeps changed Python files formatted and checked without requiring a separate manual command.

Written for Claude Code: PostToolUse hook event.

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

Reuse

Borrowing it

Nothing to install: this file belongs to jesse-smith/searchloinc. 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/jesse-smith/searchloinc/main/.claude/settings.json

Clone the repo

git clone --depth 1 https://github.com/jesse-smith/searchloinc

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.

README.md

[![agentmods](https://agentmods.dev/badge/hooks/jesse-smith/searchloinc/post-tool-use/github.svg)](https://agentmods.dev/hooks/jesse-smith/searchloinc/post-tool-use)

Your own site

<a href="https://agentmods.dev/hooks/jesse-smith/searchloinc/post-tool-use"><img src="https://agentmods.dev/badge/hooks/jesse-smith/searchloinc/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.

Your own site · 80×15

<a href="https://agentmods.dev/hooks/jesse-smith/searchloinc/post-tool-use"><img src="https://agentmods.dev/badge/hooks/jesse-smith/searchloinc/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 · 14 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "jq -r '.tool_response.filePath // .tool_input.file_path' | { read -r f; case \"$f\" in *.py) uv run ruff format \"$f\" && uv run ruff check --fix \"$f\";; esac; } 2>/dev/null || true",
          "statusMessage": "Formatting Python with ruff..."
        }
      ]
    }
  ]
}

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.

Settings file searchloinc A not measured

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.

2mo ago First seen · 14 lines scan A 2196e4fab455

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository jesse-smith/searchloinc (0 stars, last pushed 3mo 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-31.

PostToolUse next to 6 hooks from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
PostToolUsejesse-smith/searchloinc	Hook	0	3mo ago	MIT	A	—	Claude Code
PostToolUsesupabase/supabase	Hook	115k	yesterday	Apache-2.0	A	—	Claude Code
SessionStartsupabase/supabase	Hook	115k	yesterday	Apache-2.0	A	—	Claude Code
SessionStartgoogle-gemini/gemini-cli	Hook	109k	yesterday	Apache-2.0	A	—	Claude Code
PreToolUseapache/superset	Hook	75k	yesterday	Apache-2.0	A	—	Claude Code
PreToolUseanthropics/claude-cookbooks	Hook	54k	2d ago	MIT	A	—	Claude Code
PostToolUseanthropics/claude-plugins-official	Hook	46k	yesterday	Apache-2.0	A	—	Claude Code