ClaudeMods
☰
EN
● — online · Views — times
SponsorsSubmit a project
OUR GUIDES / LEARN · Updated Nov 18, 2026 · by ClaudeMods

What are Claude Code mods

What is a Claude Code mod?

A Claude Code mod (often just “Claude mod”) is a plugin that supplies a hooks module. The module registers handlers for session events and can add an interface, such as a live pane or status line, or change how a tool call is handled. A useful first mod might show a counter, track spending or add a command that explains the current workflow. The word “mod” does not mean a new model, a subscription upgrade or a guarantee of quality.

Think of it as a small tool inside a session: track spending, get a completion alert, watch agents or play a game while waiting.

Official documentation

APIs change between Claude Code versions, so follow the official pages for your installed version: Mods overview, Create a mod, Install and manage plugins and the Claude Code docs home. ClaudeMods is an independent directory of community builds; it is not endorsed by or affiliated with Anthropic.

Install a mod with /plugin

  1. Open the build page and read the original source, README and permission level.
  2. Inside Claude Code, run /plugin to browse marketplaces and installed plugins, or use the command line:
claude plugin marketplace add owner/repo
claude plugin install plugin-name@marketplace-name
  1. Replace owner/repo, plugin-name and marketplace-name with the values the author documents. Not every repository includes a marketplace; if it does not, follow the README or try a local directory with the --plugin-dir option your CLI supports.
  2. Restart or reload the session if the author says so, confirm the behavior, then add the next mod. To remove one, follow claude plugin --help and the README.

More detail: How to install a mod.

Mods vs plugins vs hooks vs skills

TermWhat it isTypical use
PluginThe package you install. It can bundle skills, hooks, mods and more.Share a set of tools through a marketplace or repository
ModA plugin that supplies a hooks module with function hooks: session events plus an optional interface.Status line, dashboard, counter, alerts, small games
Classic hookA configured action that runs when an event fires, often a shell command.Validate a change, run a formatter, send a notification
SkillInstructions and resources that teach Claude a reusable procedure.Release review, a house style, a checklist

See mods vs hooks vs skills vs MCP for a longer comparison.

Permission levels L0–L3

ClaudeMods labels each build with a scan level. These are directory scan levels, not Anthropic permission modes, a sandbox or a certification.

LevelDetected capability
L0Display or pure logic
L1Read files or environment
L2Write, execute or alter tool behavior
L3Network or model access

A lower level does not prove the code is harmless, and an unscanned build needs extra inspection. Read mod security: L0–L3 explained and try the permission scanner.

Three files to check

  • .claude-plugin/plugin.json: plugin name, version and other metadata.
  • hooks/hooks.json: declares the function modules to load through its modules array.
  • register.tsx: the actual event and interface registration code.

A repository can contain several plugins; install the intended directory rather than assuming everything at the root is the mod. Check dependencies as well as the entry file.

Choose a modest first experiment

Start with a read-only display in a disposable project. A persistent dashboard is useful when you need information during work, while a one-off automation may be simpler as a classic hook. Disable the mod if it interferes with other plugins, and avoid granting permissions you cannot explain.

Find and evaluate a candidate

Browse a category, open the original source and check recent maintenance. Stars indicate interest, not safety. Scan results describe visible source patterns and can miss dynamically loaded code. Keep a record of what you installed and how to remove it. Ready to build your own? Read write a Claude Code mod in TypeScript.

Popular Claude Code mods

Published builds ranked by community votes, then GitHub stars. Updated automatically.

  1. token-optimizer★ 2,981
  2. savvy-progress★ 380
  3. pixel-crew★ 4
  4. agent-flow★ 30
  5. Play chess against Claude while you work★ 33,441
  6. rainbow-week★ 2
  7. I just ported 'npx RuFlo' to the new Claude Code Mod system. It's next level. I★ 81,451
  8. ruflo-music★ 81,451
  9. cache-warmer★ 100
  10. cache-warmer★ 24

FAQ

What is a Claude Code mod?

A Claude Code mod is a plugin that supplies a hooks module. It registers handlers for session events and can add an interface such as a live pane or status line, or change how a tool call is handled. It is not a new model or a subscription upgrade.

How do I install a Claude Code mod?

Read the build's source and permission level first. Then run /plugin inside Claude Code, or use the command line: claude plugin marketplace add owner/repo, followed by claude plugin install plugin-name@marketplace-name. Use the names the author documents, since not every repository ships a marketplace.

What is the difference between mods, hooks and skills?

A plugin is the installable package. A mod is a plugin that supplies a hooks module for session events and optional interface. A classic hook runs a configured action, often a shell command, when an event fires. A skill gives Claude instructions for a reusable procedure.

Are Claude Code mods safe, and what do L0–L3 mean?

ClaudeMods scans each build and labels it L0 (display or pure logic), L1 (reads files or environment), L2 (writes, executes or alters tool behavior) or L3 (network or model access). These are directory scan levels, not a certification: a low level does not prove code is harmless, so read the source before installing.

Is ClaudeMods an official Anthropic site?

No. ClaudeMods is an independent directory of community-built mods. It is not endorsed by or affiliated with Anthropic; for official guidance see the Claude Code documentation at code.claude.com/docs.

Can I write a Claude Code mod in TypeScript?

Yes. A mod is three files: .claude-plugin/plugin.json, hooks/hooks.json and an entry such as hooks/register.tsx. The entry imports the Register type from claude-code and registers handlers for events such as session.start and command.run. Check the result with claude plugin validate and follow the declarations generated by your installed Claude Code version.

When should I use MCP instead of a mod?

MCP connects Claude to a separate tool or data service, so look at it when the missing capability lives in another service. A mod handles session events and interface inside Claude Code. A skill is for instructions and a classic hook for a fixed action; they can be combined in one workflow.

How can I try a mod safely?

Start in a disposable project with a read-only display mod, read the source and the L0–L3 level first, and make sure you can disable or remove it right away. Do not grant permissions you cannot explain, and note the installed version and how to uninstall.

Keep exploring

Browse all Claude Code mods

Claude Code mods by category

Guides