How to install Claude Code mods

• Claude Code v2.1.287 or newer (claude --version to check). Mods work in both the CLI and the desktop app.
• Function hooks enabled (early access) — see step 1.

Mods need function hooks turned on. Add this to your shell profile (~/.zshrc or ~/.bashrc):

Or in your Claude Code ~/.claude/settings.json:

Restart Claude Code after changing it.

A marketplace is a GitHub repo that lists plugins. Add the one that ships your mod:

(Replace owner/repo with the repo from the mod's page — each mod page here shows its source repository.)

Replace mod-name with the mod and marketplace with the marketplace name (e.g. /plugin install gateway-usage@cornell-ai). The @marketplace suffix disambiguates when several marketplaces ship the same name — including it always works.

The mod loads on your next session. If it registers a slash command, you'll see it in /help.

1. The badge. SAFE means read-only or cosmetic. CAUTION means it can change things — read the verdict. RISK means network or broad access — understand exactly what it sends and where.
2. The reach labels. reads files is normal. network + reads env vars together deserves a hard look at the source.
3. The source repo. Star count isn't trust, but an active repo with real issues and recent commits beats a 3-day-old upload.

This removes the plugin and its mods. Your settings and transcripts are untouched.

• Mod doesn't load → function hooks aren't enabled. Check the env var (echo $CLAUDE_CODE_ENABLE_FUNCTION_HOOKS should print 1) and restart Claude Code.
• Command not found after install → the marketplace wasn't added, the @marketplace suffix is missing or wrong, or you're typing the plugin name instead of the mod name. Check the mod page for the exact command.
• Something broke after installing → uninstall the mod first (/plugin uninstall), then check the mod's repo issues.