{"version":"2.1.269","anchor":"mods-path-segment-resolves-to-a-vendor-claude-code-mods-d","canonical_anchor":"mods-path-segment-resolves-to-a-vendor-claude-code-mods-d","heading":"\"mods\/\" path segment resolves to a vendor claude-code-mods directory for built-in hooks modules","tier":"internal","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/mods-path-segment-resolves-to-a-vendor-claude-code-mods-d","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### \"mods\/\" path segment resolves to a vendor claude-code-mods directory for built-in hooks modules\n\nBuilt-in hooks module IDs starting with 'mods\/' now resolve to a vendor claude-code-mods directory\n\n**What**\n\nInside 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.\n\n**Why**\n\nThis 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.\n\n- Area: Plugin Hooks\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}