Browse the full directory of Claude Code plugins — commands, agents, skills, MCP servers, and more.
Browse plugins →A data-backed map of how 31,904 Claude Code plugins are surfaced — browse the directory, explore marketplaces, and discover curated collections.
Claude Code's plugin ecosystem has reached a scale where discovery is itself a challenge. With 31,904 active plugins contributed by 14,357 authors, finding the right extension for your workflow means knowing where to look — and understanding how the directory organizes what's available.
This post maps the landscape: what the Claude Code plugin marketplace looks like today, where plugins are surfaced, and how you can filter the catalog to find extensions that actually match your needs. Whether you're looking for workflow automation, frontend tooling, or token optimization, the discovery channels covered here will get you there faster.
The directory currently indexes 297,317 individual components across those 31,904 plugins. Here's how the component types break down:
Growth remains steady: 2,208 new plugins were added this week, compared to 2,148 the previous week. Over the last 30 days, the directory has recorded 23,388 installs — a signal that developers are actively experimenting with extensions rather than just browsing.
Skills dominate the component distribution at roughly 59% of all components. This makes sense — skills are the most lightweight extension point, requiring only a markdown file that teaches Claude Code a new capability. The heavier integration types (MCP, LSP, hooks) represent a smaller but growing slice of the ecosystem.
To ground these numbers, here are three plugins that illustrate the range of what's available in the directory. Each serves a distinct purpose and uses different component types.
Superpowers has accumulated 198,309 stars and 1,332 installs in the last seven days, making it one of the most-installed plugins in the directory. It provides skills and hooks that enforce a structured TDD workflow — guiding brainstorming into validated specs, creating isolated git worktrees for feature branches, running parallel task execution, and inserting verification checkpoints before merging or committing. If you want Claude Code to follow a disciplined development process rather than freewheeling, this plugin adds that structure.
Caveman takes a different approach entirely. With 974 installs over the last seven days and 61,597 stars, it reduces Claude Code token usage by approximately 75% using ultra-compressed communication across conversations, code reviews, commits, and file edits. It bundles agents, skills, and hooks that preserve full technical accuracy while dramatically cutting costs. For developers running Claude Code on large codebases where token consumption adds up, this addresses a real pain point.
Impeccable occupies a specialized niche: auditing and polishing frontend interfaces. At 311 installs in the past seven days and 28,633 stars, it provides skills that critique UX, visual hierarchy, accessibility, performance, responsive behavior, theming, typography, color, motion, micro-interactions, and design systems — then generates production-grade code changes. This is a plugin for developers who want their UI reviewed by an opinionated design eye before shipping.
These three plugins span different concerns (workflow discipline, cost optimization, design quality) and different component types (skills, hooks, agents). That variety is representative of the broader catalog.
The directory offers several paths to find plugins depending on what you already know about what you're looking for.
The plugin directory is the primary entry point. It lists all 31,904 active plugins with filtering by component type, category, and sorting by stars, installs, or recency. If you have a general sense of what you need — "something for code review" or "a hook that runs on commit" — start here. The search bar supports keyword queries, and the component-type filters let you narrow results to just plugins that provide, say, MCP servers or agents.
The marketplaces page surfaces plugin collections organized by publishers and communities. Marketplaces group plugins around a theme or authoring organization, making them useful when you want to explore a particular author's full offering or find plugins that were designed to work together. Think of marketplaces as storefronts within the larger directory — they give authors and communities a way to present their plugins as a coherent set rather than scattered individual listings.
Collections are user-curated lists of plugins organized around workflows or use cases. Unlike marketplaces (which are publisher-oriented), collections are assembled by developers who've tested plugins together and grouped them by practical purpose. If you're looking for "plugins I need for a Python microservices project" or "everything useful for code review," collections are where community curation happens.
If you know the specific extension point you need — an MCP server to connect Claude Code to your database, or a hook to enforce linting on save — filtering by component type cuts through the noise. The directory's component-type facets map directly to Claude Code's extension architecture: commands, agents, skills, hooks, MCP servers, LSP servers, output styles, themes, and monitors. This is the most precise discovery path when you already know what kind of integration you're building.
The directory tracks both GitHub stars and weekly install counts. Stars indicate broad interest (Superpowers has 198,309), while install counts reflect active adoption (Superpowers logged 1,332 installs in the past seven days). Neither metric tells you whether a plugin is right for your workflow, but together they help distinguish actively maintained, widely used plugins from dormant experiments. Sorting by 7-day installs is the most useful signal for current momentum.
The Claude Code plugin marketplace has grown to 31,904 plugins across 297,317 components, contributed by over 14,357 authors. The discovery surface isn't a single storefront — it's a combination of the full directory, publisher marketplaces, and community collections, each serving different discovery patterns.
For developers evaluating plugins to install, the practical approach is: start with the directory's component-type filters if you know what extension point you need, browse collections if you want workflow-oriented groupings, and check marketplaces for publisher-curated sets. Use install counts and stars as tiebreakers, not as the primary signal — what a plugin actually does matters more than its popularity.
With 2,208 new plugins appearing each week, the catalog continues to expand. The challenge has shifted from "are there plugins for this?" to "which of these plugins fits my specific workflow?" The discovery tools exist to answer that question.
Enforces a structured TDD workflow with parallel task execution, code review, and root-cause debugging. Guides brainstorming into validated specs, creates isolated git worktrees for feature branches, and runs verification checkpoints before merging or committing.
Cuts Claude Code token usage by ~75% using ultra-compressed caveman-style communication across conversations, code reviews, commits, and file edits while preserving full technical accuracy.
Audit, critique, and polish frontend interfaces with production-grade code changes covering UX, visual hierarchy, accessibility, performance, responsive behavior, theming, typography, color, motion, micro-interactions, and design systems.