PostToolUse

PostToolUse is a hook for Claude Code from Nisus74/humanise. Its token cost is not measured, scanned A, original, MIT.

An automatic after-edit hook that runs a documentation writing check whenever a file is written or edited. A hook is a script triggered automatically by a tool event.

In plain words
What is it for?
Use it in the humanise repository to inspect docs after edits and run the post-edit checker through Bash. It is intended for documentation changes, not general application behaviour.
Why use it?
It catches writing problems immediately after documentation changes instead of relying on a later manual review. The check supports the humanise project's own writing workflow.

Hook for Claude Code

Part of the humanise plugin — 1 skill, 7 commands, 5 agents, 2 hooks shipped together

One of 3 entries in settings.json — they are configured in one file and arrive together.

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/nisus74/humanise/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/Nisus74/humanise

Made for: Claude Code.

Or install humanise, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 5 agents, 2 hooks.

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 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 3d 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 · 15 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/post-edit.sh\"",
          "timeout": 120,
          "statusMessage": "Dogfooding the humanise checker on docs"
        }
      ]
    }
  ]
}
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.

  1. 3d ago First seen · 15 lines scan A 4da72e84e892

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository Nisus74/humanise (1 stars, last pushed 6d 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.