9 Claude Code Plugins That Actually Ship — and the Ones to Skip
Claude Code's plugin surface is large but uneven; installing the wrong set produces conflicts and lag, not productivity. This selection draws a line between real infrastructure (LSP-backed type awareness, write-time security interception) and noise, giving teams a shortlist that actually reduces rework and repetitive configuration across sessions.
The Claude Code plugin marketplace has ballooned to hundreds of entries, but most are single-purpose and thin. Nine plugins — a mix of Anthropic official tools and community standouts — form a coherent stack across environment setup, security, code quality, capability expansion, and long-running project memory. security-guidance intercepts hardcoded secrets and SQL injection at write time rather than after the fact. The LSP pack gives Claude Code IDE-grade type inference and definition navigation, eliminating guesswork on strongly-typed codebases. Strix runs white-hat penetration tests pre-deployment, while code-review flags logic gaps and hidden defects that pass tests but fail review. On the expansion side, Frontend Design overrides Claude Code's templated UI generation with layout-aware styling, and Agent Reach scrapes public web data without API keys. claude-mem persists compressed session history across terminal restarts so multi-session projects don't start from zero every time. The piece also warns that installing everything at once causes command conflicts and latency, and it pitches ServBay's AI gateway as a model-routing layer for teams that switch between multiple coding agents mid-project.
The real dividing line in Claude Code's plugin ecosystem is between tools that operate at code-generation time (security-guidance, code-review) and tools that operate before or after (Strix, claude-mem). The write-time interceptors change the default safety posture more than post-hoc scanners because they prevent vulnerable code from ever landing in the repo.
The LSP pack is underrated as infrastructure: it doesn't produce visible output, but it fixes the largest source of AI-generated bugs in typed languages — hallucinated types and broken call chains — by grounding Claude Code in the same AST-level information an IDE uses.
Agent Reach's keyless scraping model is notable because it sidesteps the API-key provisioning headache that blocks most data-acquisition workflows in AI coding tools. The tradeoff is that it only works on publicly accessible pages, but that covers a large surface of real-world data tasks.
claude-mem addresses a structural weakness of terminal-based AI coding: every session is amnesic by default. Persistent compressed memory turns Claude Code from a stateless tool into something that can carry context across weeks of iteration, which matters more for maintenance-phase work than for greenfield prototyping.
The warning against installing all plugins at once is a genuine operational constraint, not just advice. Plugin conflicts and latency in an agentic coding tool directly degrade the speed and correctness of code generation, so curation is a performance concern, not just a preference.