What is a Claude Code mod?

Since version 2.1.287, a mod is a Claude Code plugin with JavaScript or TypeScript handlers that run inside Claude Code. Unlike a settings hook or a status line script, a mod can draw panes beside the transcript and bands above the prompt, add buttons and toasts, restyle the spinner and tool rows, and hold, rewrite or answer a tool call. Mods work in the CLI, the Code tab of the desktop app and the VS Code extension.

How do I install a Claude Code mod?

A mod installs like any plugin. Inside Claude Code, add its marketplace with /plugin marketplace add owner/repo, then run /plugin install name@marketplace. To try one without installing it, clone the repo and start Claude Code with --plugin-dir pointing at the mod folder. Every mod page here has the exact commands.

What else is in this directory?

Every other way people customise Claude Code: status line scripts, settings hooks, custom slash commands, output styles, themes, plugin marketplaces and workflow kits, plus the apps people run it with, such as GUIs and mobile clients, usage and cost trackers, session browsers, model routers, multi-agent and worktree runners and editor integrations. Skills and MCP servers have their own directories.

What does a mod's reach mean?

Reach is the widest thing a mod's code asks Claude Code to do, from a static scan of its source: L0 only draws and remembers, L1 reads files or settings, L2 writes files, runs processes or drives Claude, and L3 reaches the network. It is a footprint, not a verdict: a pull request tracker has to run git. A mod runs with your permissions, so read its code before you install it.

How is popularity measured?

By the GitHub stars of each repo, with forks, curated awesome lists and listing in Anthropic's plugin directory as smaller signals. When one repo holds many mods they share its stars, so only its first few rank high. The data refreshes every day.

Are Claude Code mods safe?

Mods, hooks, status lines and most tools run on your machine with your permissions, so treat them like any code from the internet: check a mod's reach, read the code before installing, prefer well-starred and recently updated repos, and check the license. Run claude plugin validate on a clone to list what a mod hooks and calls without running it, and start Claude Code with --safe-mode to turn every customization off for a session.

Claude Code Mods: 8,000+ Status Lines, Hooks, Plugins & Tools

6,784 mods

desktop-tool-pulse

109

whyashthakker/awesome-claude-code-mods

Chart completed tool latency and failures by tool.

desktop-tool-pulse

desktop-turn-chart

edit-heatmap

error-inbox

file-tree

hash-lab

ignore-check

json-format

link-shelf

markdown-map

quota-watch

release-checklist

scope-watch

scratchpad

snippet-shelf

staged-review

stash-browser

stopwatch

task-board

text-counter

time-lab

todo-finder

tool-timing

uuid-lab

worktree-map

terminal-browser

thermal

gas-gauge

recall-cue

doc-drift-watch

pro-hud

agent-progress

all-mods

barra-creditos

blast-radius

blast-radius

blast-radius

cc-context-mod

cc-image-view

cells

checkpoint

claw-hud

close-gate

cm-git-branch

code-index

collision-guard

commit-drift

commit-erinnerung