Under the hood
No documentation found
Built-in hooks module IDs starting with 'mods/' now resolve to a vendor claude-code-mods directory
What
Inside the function that turns a builtin-hooks-module: identifier into an actual file path, a new rule checks whether the remainder of the identifier starts with mods/. If it does, the path resolves under vendor/claude-code-mods/mods instead of the normal built-in hooks location.
Why
This lets Claude Code load hook modules from a separate vendored claude-code-mods directory when they're referenced with a mods/ path, alongside its regular built-in hooks.