Installs Claude Code Mods with one command A catalog of 38 Claude Code "Mods" has launched on aitmpl.com, letting developers install function-hook plugins with a single npx command instead of packaging and publishing them through a plugin marketplace. Each Mod runs in a sandboxed module that receives the engine object, event and next continuation, allowing it to inspect, rewrite or deny tool calls, with access to UI, HTTP, filesystem and other capabilities routed through the engine. The catalog spans security, workflow, UI, caching, integration and game categories, and requires the CLAUDE_CODE_ENABLE_FUNCTION_HOOKS flag. Mods let you hook into Claude Code while it works: block a command, rewrite a tool call, redact a secret from a result, or draw a live pane above the prompt. Until recently that meant writing the module yourself, packaging it as a plugin and publishing a marketplace. The Mods catalog on aitmpl.com https://www.aitmpl.com removes those steps: 38 mods, one command each. A Mod is a Claude Code plugin whose behavior lives in a function-hooks module. A shell hook reacts to an event after the fact. A function hook wraps the event: your function receives the engine object $ , the event e , and a next continuation, and decides what happens. That gives three positions instead of one: next e and inspect what came back. next { ...e, input } with changed data, or change the result on the way out. { deny: "reason" } and never call next . The tool does not run. The module runs in a sandbox of its own, with no DOM and no Node. Everything outside it goes through $ : $.ui , $.http , $.fs , $.process , $.state , $.store , $.session , $.command , $.tool , $.model and $.clock . That is what makes a mod more than a filter. Mods are distributed as plugins. The standard route is a plugin marketplace a repo with .claude-plugin/marketplace.json : /plugin marketplace add