Use it in projects that have this hook configured and need a lint check after Edit or Write operations.

It can catch code or formatting problems immediately after an edit, before they are overlooked.

How vericontext/vibeframe configures Claude Code

vibeframe: Hook for Claude Code

.claude/settings.json

PostToolUse is a hook for Claude Code from vericontext/vibeframe. Its token cost is not measured, scanned A, a copy of SessionStart, MIT.

An automated check that runs after files are edited or written. It executes a shell script called post-edit-lint.sh from a project’s Claude hooks folder.

In plain words

What is it for?: Use it in projects that have this hook configured and need a lint check after Edit or Write operations.
Why use it?: It can catch code or formatting problems immediately after an edit, before they are overlooked.

Written for Claude Code: $CLAUDE_PROJECT_DIR variable.

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

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

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/vericontext/vibeframe

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/vericontext/vibeframe/post-tool-use/github.svg)](https://agentmods.dev/hooks/vericontext/vibeframe/post-tool-use)

Your own site

<a href="https://agentmods.dev/hooks/vericontext/vibeframe/post-tool-use"><img src="https://agentmods.dev/badge/hooks/vericontext/vibeframe/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/vericontext/vibeframe/post-tool-use"><img src="https://agentmods.dev/badge/hooks/vericontext/vibeframe/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 47% copy Near-identical to another mod 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.

Origin

This is a copy

47% identical to SessionStart — 9 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/settings.json · 13 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/post-edit-lint.sh\""
        }
      ]
    }
  ]
}

Same file

What else `settings.json` configures

This page is one entry in a file that holds 3. 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.

2mo ago First seen · 13 lines scan A 9ac8dc777584

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository vericontext/vibeframe (185 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. It is 47% identical to SessionStart, differing in 9 lines, and is treated as a copy.

ai ai-agents claude cli developer-tools ffmpeg

PostToolUse next to 6 hooks from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
PostToolUsevericontext/vibeframe	Hook	185	yesterday	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