Hookify
Create local rules that warn about or block matching tool actions.
Run logic when an event happens. The name “hook” covers two different mechanisms, so start by choosing where the code should run.
Settings hooks are configured in settings.json or a plugin hooks configuration. They run lifecycle logic through supported commands, HTTP requests or prompt-based handlers. They are useful for a script that should run at a known event.
A mod’s hooks are JavaScript or TypeScript functions inside Claude Code. They can observe or change events and draw interface elements. The official Mods documentation calls the settings-file mechanism “settings hooks” to keep the distinction clear.
This release offers a substantive guide and links to Hookify, Security Guidance and the Hook Development skill. We do not present these packages as standalone hook scripts. Review generated rules and event definitions before enabling them.
Read the source. Check the requirements. Compare what fits.
Create local rules that warn about or block matching tool actions.
Edit warnings and model-assisted reviews for common vulnerability patterns.
Author lifecycle hooks with guidance on event selection, configuration and validation.
A Hookify skill for defining readable rules with event and pattern conditions.
Source review: October 5, 2026. Listings are documentation reviews, not runtime tests or security audits. Our editorial method
Choose an install scope and check the prerequisites first.
Read the installation guide