PostToolUse

PostToolUse is a hook for Claude Code from SergeiGorbatiuk/startup-superpowers. Its token cost is not measured, scanned A, original, GPL-3.0.

A hook that runs after file-editing tools finish. It executes validation scripts for project documents such as hypotheses, interview plans, surveys, and MVP plans.

In plain words
What is it for?
Use it to trigger document checks after Edit, Write, or apply_patch calls, including validation of core, competitor, hypothesis, interview, survey, MVP, and audience-map files.
Why use it?
It can catch formatting or content problems immediately after changes are made. The input does not describe what each validation script checks.

Hook for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the startup-superpowers plugin — 9 skills, 4 agents, 2 hooks shipped together

One of 2 entries in hooks.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/sergeigorbatiuk/startup-superpowers/post-tool-use
Clone the repo
git clone --depth 1 https://github.com/SergeiGorbatiuk/startup-superpowers

Made for: Claude Code.

Or install startup-superpowers, the plugin that ships this one along with the rest of its 9 skills, 4 agents, 2 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/sergeigorbatiuk/startup-superpowers/post-tool-use.svg)](https://agentmods.dev/hooks/sergeigorbatiuk/startup-superpowers/post-tool-use)
Your own site
<a href="https://agentmods.dev/hooks/sergeigorbatiuk/startup-superpowers/post-tool-use"><img src="https://agentmods.dev/badge/hooks/sergeigorbatiuk/startup-superpowers/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 unknown 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 6d 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 · 57 lines

The source is not reproduced here

Licensed GPL-3.0

The repository is licensed GPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Same file

What else hooks.json configures

This page is one entry in a file that holds 2. 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. 6d ago First seen · 57 lines scan A 45eb05ba8984

Subscribe to this mod's changes

PostToolUse is a hook published in the GitHub repository SergeiGorbatiuk/startup-superpowers (24 stars, last pushed 1mo ago), licensed GPL-3.0. 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-30.