PostToolUse

PostToolUse is a hook for coding agents from camilooscargbaptista/cto-toolkit. Its token cost is not measured, scanned A, original, MIT.

A set of actions that run after files are written or edited. They execute checks for code changes, Dockerfiles, database migrations, and tests.

In plain words
What is it for?
Checking edited code, Dockerfiles, SQL migration files, and test files for issues such as unsafe container settings, risky migrations, and test-quality problems.
Why use it?
It catches selected safety, formatting, and configuration problems immediately after edits are made.

Hook

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the cto-toolkit plugin — 54 skills, 6 agents, 3 hooks shipped together

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

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add camilooscargbaptista/cto-toolkit
Claude Code
/plugin install cto-toolkit

Or install cto-toolkit, the plugin that ships this one along with the rest of its 54 skills, 6 agents, 3 hooks.

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.

agentmods badge for PostToolUse

README.md
[![agentmods](https://agentmods.dev/badge/hooks/camilooscargbaptista/cto-toolkit/post-tool-use.svg)](https://agentmods.dev/hooks/camilooscargbaptista/cto-toolkit/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/camilooscargbaptista/cto-toolkit/post-tool-use"><img src="https://agentmods.dev/badge/hooks/camilooscargbaptista/cto-toolkit/post-tool-use.svg" alt="Measured on agentmods" 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. 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 5d 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.

hooks/hooks.json · 49 lines

What it actually says

{
  "PostToolUse": [
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/post-edit-check.sh"
        }
      ]
    },
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "prompt",
          "prompt": "If the file just written is a Dockerfile, verify: (1) uses non-root USER, (2) has multi-stage build if applicable, (3) no secrets in ENV/ARG, (4) uses specific image tag (not :latest). Report only if issues found."
        }
      ]
    },
    {
      "matcher": "Write",
      "hooks": [
        {
          "type": "prompt",
          "prompt": "If the file just written is a SQL migration (*.sql), verify: (1) filename follows NNN_description.sql pattern, (2) CREATE INDEX uses CONCURRENTLY, (3) no ADD COLUMN NOT NULL without DEFAULT on existing tables, (4) no DROP TABLE without confirmation. Report only if issues found."
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "prompt",
          "prompt": "If the file just written/edited is a test file (*.spec.ts, *.test.ts, *_test.go, *_test.py), verify: (1) tests have descriptive names, (2) mocks are not hardcoded with magic values, (3) edge cases are covered (null, empty, boundary), (4) no console.log left in tests. Report only if issues found."
        }
      ]
    },
    {
      "matcher": "Write|Edit",
      "hooks": [
        {
          "type": "command",
          "command": "${CLAUDE_PLUGIN_ROOT}/hooks/scripts/model-routing-check.sh"
        }
      ]
    }
  ]
}
Same file

What else hooks.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. 5d ago First seen · 49 lines scan A 028b26684420

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository camilooscargbaptista/cto-toolkit (7 stars, last pushed 5mo 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.