A set of automatic checks that run after Bash commands or file edits and writes, using shell scripts to validate output, detect low-quality text, and review language.

It helps validate command results, review edited files, detect unwanted filler, and check written language after changes.

It catches problems immediately after an agent changes files or runs commands, before the work is considered finished.

PostToolUse — Hook by 5uck1ess

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/5uck1ess/devkit/post-tool-use

Clone the repo

git clone --depth 1 https://github.com/5uck1ess/devkit

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 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.

hooks/hooks.json · 48 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Bash",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/post-validate.sh",
          "statusMessage": "Validating output...",
          "timeout": 10
        }
      ]
    },
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/post-validate.sh",
          "statusMessage": "Validating write...",
          "timeout": 10
        }
      ]
    },
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/slop-detect.sh",
          "statusMessage": "Slop check...",
          "timeout": 5
        }
      ]
    },
    {
      "matcher": "Edit|Write",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/lang-review.sh",
          "statusMessage": "Code quality check...",
          "timeout": 5
        }
      ]
    }
  ]
}

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 · 48 lines scan A 6ea40dc694f7

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository 5uck1ess/devkit (5 stars, last pushed 13d 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.

Code review Multi-Agent Productivity ai-agents claude-code code-quality developer-tools

PostToolUse

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other hooks, from other repositories

PreToolUse

PostToolUse

PreToolUse

SessionStart

TaskCompleted

PreToolUse