AI Coding Agent Hooks

A hook is a shell script your AI coding agent runs automatically at a defined event — before a tool call, after a file edit, before a shell command executes. Used well, hooks enforce the policy you can't rely on a prompt alone to guarantee: block a secret before it's committed, log every tool call for an audit trail, or require a second check before a production command runs. Every hook below is real, copy-paste code — not a concept.

100 hooks · Written for Claude Code's documented hook contract

New to agent hooks? Read the security risks first →

6 results Clear filters →

📁 File & Environment Change Monitoring

6 hooks

Catches drift on disk and in config that a tool-call log alone won't show — a file edited outside the agent, a directory added mid-session, a symlink swapped underneath a watched path.

Alert on .env File Change Outside a Hook-Controlled Edit

Security

Flags whenever a watched .env or .envrc file changes on disk, regardless of what triggered it.

FileChanged · Claude Code

Block Project-Settings Changes Without a Reviewer Flag

Security

Blocks a change to the project's checked-in .claude/settings.json unless a reviewer env var is set.

ConfigChange · Claude Code

Detect a Symlink Swap on a Watched Compliance File

Security

Flags if a newly-created file at a watched path is actually a symlink pointing outside the repo.

FileChanged · Claude Code