A set of hooks that run after writing, editing, or multi-editing files. They check specification compliance, require tests, and validate authoring documents.

Use it in projects where edits must be checked against specifications, accompanied by tests, and kept consistent with required documentation.

It helps enforce project rules and test coverage immediately after code or documentation changes.

PostToolUse — Hook by aziontech

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/aziontech/webkit/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/aziontech/webkit

Made for: Claude Code.

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 89% 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 yesterday.

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

89% identical to PreToolUse — 25 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 · 21 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit|MultiEdit",
      "hooks": [
        {
          "type": "command",
          "command": "node .claude/hooks/validate-spec-compliance.mjs"
        },
        {
          "type": "command",
          "command": "node .claude/hooks/enforce-test-exists.mjs"
        },
        {
          "type": "command",
          "command": "node .claude/hooks/validate-authoring-docs.mjs"
        }
      ]
    }
  ]
}

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.

yesterday First seen · 21 lines scan A ac4b1a4938db

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository aziontech/webkit (2 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. It is 89% identical to PreToolUse, differing in 25 lines, and is treated as a copy.

Frontend Testing Writing and docs component-library frontend-platform monorepo ui-architecture workspace

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

This is a copy

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

SessionStart

PreToolUse

PostToolUse

Stop

SessionStart

PostToolUse