claude-modderlisted

Build, debug, test, review and govern Claude Mods - Claude Code plugins that keep their logic in a TypeScript hooks module of function hooks (register(on, options); hooks ($, e, next) composed like Koa middleware over the engine interface $). Use it whenever the user mentions Claude Mods, mods, function hooks, a hooks module, "modules" in hooks.json, on("tool.call"), $.ui / $.tool / $.fs, next(e), next.to, .catch, /plugin-types, claude plugin test, CLAUDE_CODE_ENABLE_FUNCTION_HOOKS, ui.render, panes, engine.create, prependPlugins or sec-default. Also use it when they want to change Claude Code deeply in code, even if they only say "hook", "plugin" or "extend Claude Code". Examples - deny or rewrite tool calls, redact tool output, add tools, slash commands, panes or status lines, reshape prompts, system prompt sections or model output, audit every action, enforce org policy. Not for plain shell hooks in settings.json unless they are wrapped or migrated.
4refael/marketplace · ★ 0 · AI & Automation · score 72

Install: claude install-skill 4refael/marketplace

# Claude Mods (function hooks) A **Claude Mod** is a normal Claude Code plugin that keeps its logic in a **hooks module**: one TypeScript/JavaScript file that `hooks/hooks.json` names under `"modules"` and that exports `register(on, options)`. "Function hook" is the engineering primitive, and "Mod" is the product name for a plugin that uses it. A mod can rewrite almost everything Claude Code does, including tool calls, prompts, system prompt sections, the model's streamed output, slash commands, the config menu and what the terminal or desktop app draws. Every side effect goes through one audited object, `$`. ## Step 0: make sure Claude Mods are turned on Do this before any other mod work. This skill runs on other people's machines, so do not assume the flag is on. Paths such as `scripts/check-enabled.sh`, `references/...` and `assets/...` are relative to this skill's folder, which depends on how it was installed (`~/.claude/skills/claude-modder/`, a project's `.claude/skills/claude-modder/`, or a plugin cache folder). 1. Run `scripts/check-enabled.sh` (bash; macOS, Linux, WSL). It runs `claude plugin test` on an empty temporary folder, the same gate the loader uses, and it reports on the environment and config dir (`CLAUDE_CONFIG_DIR` or `~/.claude`) that the next `claude` process gets. Exit codes and meaning: | Exit | State | What to do | |---|---|---| | 0 | **ON**. It prints the version and where the flag comes from | Go on. If it warns that the build is olde