Best Claude Code Plugins in 2026: We Installed Them and Measured

TL;DR: We installed the plugins everyone keeps recommending and measured what we could. The keepers: Caveman for output-token compression (65% average cut, with a real caveat), CodeBurn for seeing where your money goes, Morph for fast code applies, Superpowers for planning, and a handful of official Anthropic plugins. Skip the "install 20 plugins" advice; every one you add eats context.

There's a thread on r/ClaudeCode that asks the question every roundup dodges: "what are the best Claude Code plugins right now? Does anyone actually measure?"

Fair. Almost nobody does. The typical listicle is ten GitHub links and zero numbers. So when we added Caveman to our tool directory this week, we didn't just read the README. We vendored the skill into our own pipeline, ran it live in a working session, and pulled the benchmark data from the repo. This roundup is built on that, plus verified numbers for everything else on the list.

One more thing before the list, because it reframes what these plugins are actually for. On a normal day we run three to five repos in parallel, each with five or more Claude sessions open, juggled through voice input (Wispr Flow) and cmux to keep the overview. To give you a sense of that scale: we're on the Max 5x plan and the whole week's usage is gone in a day and a half, sometimes two. That's not one person chatting a lot, that's a fleet of agents shipping a week of work in two days. We're not alone either; there's a well-trafficked GitHub issue full of Max users depleting weekly quotas in days. But the scarcer budget at fleet scale is attention: every context switch means reading another long summary of what an agent just did, and that reading builds fatigue fast. The plugins that matter most aren't the ones that save tokens; they're the ones that save human attention. Tokens are just the number we can measure.

Plugins vs skills, in one minute

Quick vocabulary so the rest of this makes sense. A skill is a Markdown file that teaches Claude Code a behavior: how to compress output, how to write Obsidian markdown, how to plan before coding. A plugin is the bigger container. It can bundle skills plus slash commands, hooks, subagents, and MCP servers, and it installs from a marketplace with one command:

/plugin marketplace add anthropics/claude-plugins-official
/plugin install frontend-design@claude-plugins-official

Anthropic runs an official plugin directory and an official skills repo. The community ecosystem around them is enormous: one index tracked 15,134 plugin repos by May 2026, up from around 4,000 a year earlier.

That growth is exactly why a filter matters. Here's ours.

The quick picks

Now the detail, including the caveats the listicles skip.

1. Caveman: the token saver with an honest asterisk

Caveman is a skill that makes Claude Code answer like a smart caveman. Articles, filler, and pleasantries die; code, commands, and error strings stay byte-for-byte exact. It went from zero to 86.9k GitHub stars because the pitch is irresistible: same answers, 65% fewer output tokens.

Here's why it earned the top slot for us, and it isn't the token bill. We'd been telling Claude for months to "keep answers short and bulleted, no fluff" in ad-hoc instructions, the way most people do. It half-works, then decays. Caveman is that instruction turned into an actual enforced system: precise rules about what dies (articles, hedging, tool-call narration) and what survives untouched (code, commands, exact error strings). When you're switching between a dozen agent sessions, terse answers are the difference between scanning a status in two seconds and wading through three paragraphs to find the one line that matters.

We installed it through our own skill pipeline and ran it live for an afternoon of real work. Three things stood out.

First, it works as advertised on chatty tasks. The repo's benchmarks show 294 output tokens vs 1,214 for the same answers, and the style rules are smarter than the meme suggests. It bans fake abbreviations like cfg and impl because the tokenizer splits them anyway (zero tokens saved, harder to read), and it automatically drops back to full prose for security warnings and destructive-action confirmations.

Second, the asterisk. Caveman compresses output tokens only. Input and reasoning tokens are untouched, and the skill itself injects roughly 1 to 1.5k input tokens per turn. The README says this plainly: whole-session savings run smaller than the headline, and on already-terse workloads they can go net negative. You'll also see a "75%" figure floating around third-party coverage; that's not the official claim. 65% average, output only.

Third, drift. Install the skill alone and Claude will slip back into full verbose prose mid-session, usually right when it writes a long wrap-up summary. We watched it happen in our own session within an hour. The maintainers know: a comment in the hook source notes that models "drifted back to verbose mid-conversation" when the rules were injected only once. The fix ships with the repo: a session-start hook that loads the full ruleset plus a per-prompt hook that re-anchors the mode on every message. We wired both into our setup, tested activation, deactivation, and a per-repo opt-out (.caveman.json with "defaultMode": "off"), and the drift stopped. If you install Caveman, install the hooks; the skill file alone won't hold.

Install is one command (or literally one Markdown file plus the two hooks if you manage skills yourself), with six intensity levels from lite to wenyan, which compresses into classical Chinese. Greg Isenberg featured it in his "3 claude code plugins to save you tokens" video the day before we wrote this, so expect the star count to keep climbing.

Verdict: install it if your sessions are long and Claude's answers are chatty. Measure a week with it on and off before you trust the headline number. Which brings us to the tool for measuring.

2. CodeBurn: see where your tokens actually go

You can't optimize what you don't measure, and most people genuinely don't know whether their Claude Code spend goes to output, reasoning, or re-reading the same files. CodeBurn fixes that: a free, open-source, local-first tracker that breaks down token usage and cost across 31 tools including Claude Code, Cursor, Codex, and Copilot, by model, project, and task.

npx codeburn@latest
# or
brew install codeburn

Everything stays on your machine, which matters if your prompts contain client code. It's the natural companion to Caveman: run CodeBurn for a baseline week, add Caveman, compare. That's the measurement the Reddit thread was asking for, and it takes ten minutes to set up.

Verdict: install it first, before any optimizer. Baselines beat vibes.

3. Morph: fast applies and compact context

Morph attacks token waste from a different angle: instead of making Claude talk less, it makes edits and context cheaper. The Fast Apply layer processes code edits at a claimed 10,500+ tokens per second with 98% first-pass accuracy, and the Claude Code plugin adds Flash Compact for context compression. WarpGrep, their code search, is free for 100k requests and $1 per million after.

Worth knowing: the plugin enables the compaction piece, while Fast Apply and WarpGrep come through the MCP, so you want both installed. Their docs walk through the Claude Code setup.

Verdict: most useful on large codebases where applies and searches dominate your token bill. Overkill for small projects.

4. Superpowers: make Claude think before it codes

Superpowers by Jesse Vincent is the planning layer most people bolt on after their first "Claude dove straight into code and refactored the wrong thing" incident. Brainstorming, spec writing, task breakdown; it forces a plan-first loop. At 94k stars it's the most-adopted community framework, and it's been accepted into the official marketplace, which says something about where Anthropic thinks workflows are heading.

Verdict: the highest-leverage plugin on this list if your problem is direction rather than cost.

5. The official picks worth keeping

A 130+ comment r/ClaudeAI thread went through the official plugins most people never open. The consensus impactful four: typescript-lsp (real language-server intelligence instead of guessing), security-guidance (scans before you ship), context7 (up-to-date docs injection so Claude stops hallucinating APIs), and playwright (browser testing in plain English).

From our own use we'd add frontend-design, Anthropic's plugin for killing the generic AI look in UIs, and skill-creator, which turns your repeated corrections into reusable skills. That last one is the meta-move: the best plugin is often the one you generate for your own workflow.

Verdict: start here if you install nothing else. Official, free, maintained.

6. Obsidian Skills: if your notes are your second brain

Not a token saver, but it earns its slot. Obsidian Skills is the official five-skill pack by Obsidian CEO Steph Ango that teaches Claude Code proper Obsidian markdown, Bases databases, JSON Canvas, and the CLI. If your project notes live in a vault, this is the difference between Claude writing markdown at your vault and writing markdown that belongs in it. We reviewed it in depth in our Obsidian Skills review.

Where to find more (without drowning)

The prompt-skills category in our directory tracks the skill packs we've vetted. Beyond that, the ecosystem has real infrastructure now:

• Skills.sh: Vercel Labs' open directory and leaderboard, installs via npx skills add
• anthropics/claude-plugins-official: the curated official set
• awesome-claude-code: the canonical hand-curated list, 36.8k stars
• ClaudePluginHub: directory that rates plugins for quality, freshness, and safety
• claudemarketplaces.com: cross-agent skills, plugins, and MCP servers

One warning from experience: browsing these is fun, and that's the trap.

The pitfall nobody prices in: plugin bloat

Every skill you install injects instructions into your context. Ten skills can quietly cost you more input tokens per turn than Caveman saves in output. The math only works if you're selective.

Our rule of thumb after running a 120-plus skill pipeline internally: three to five active plugins per project, chosen for that project. Take a baseline with CodeBurn, add one thing at a time, and delete anything that hasn't earned its context window in a week. Boring advice, measurable results.

FAQ

What are the best Claude Code plugins for beginners? Start with the official marketplace: typescript-lsp, security-guidance, and context7. Add Caveman once you've watched a week of token spend.

Do plugins cost money? The skills and plugins in this list are free and open source. Morph's backend services are usage-based beyond the free tier, and Claude Code itself needs an Anthropic plan.

Skill or plugin, which should I build for my own workflow? Start with a skill; it's one Markdown file. Graduate to a plugin when you need slash commands, hooks, or an MCP server bundled in.

Does Caveman work with agents other than Claude Code? Yes, the repo ships install scripts for 30+ agents including Cursor, Windsurf, Cline, Gemini CLI, and Copilot.

The bottom line

The best Claude Code plugins in 2026 aren't the flashiest ones, they're the ones that save your attention and can prove it. Track spend with CodeBurn, compress output with Caveman (hooks included, knowing exactly what the 65% does and doesn't cover), plan with Superpowers, and keep the official four running underneath. Then stop installing things. The token bill is measurable; the real win is ending the day less tired.

Got a plugin that survived your own measurement? We're collecting real numbers for the next update of this piece; the tool directory is where the vetted ones land.