Modes plugged into Claude Code: power in the kitchen, not the display

Anthropic brought plugin support to Claude Code. The feature is in public beta. Plugins consist of slash commands, agents, MCP servers, and hooks. Teams pass their setups to each other this way. Plugins count as light packages. They switch on and off per job. Separately for debugging, testing, and deployment. Speed rises when idle ones close. Teams enforce code rules through plugins. They connect to internal systems over MCP. The framework ties packaging work to one shape. Modularity and collaboration stand together. So the power sits in the kitchen, not the display case. Setup trouble ends. Choosing trouble begins. The menu crowds. ^{[1] [2]}

My question is set. Who will maintain this six months from now. Installing a plugin takes a day. Keeping it alive takes every day. Every liked setup writes a maintenance debt. If nobody owns the debt, the order turns into a junkyard. Dotfiles existed before. Now marketplaces exist. The name changed, the trouble stayed. Ownerless settings rot. Rotten settings cause night outages. Every team learns this once through bitter experience. I hope someone keeps the ledger this time. Who keeps the ledger lives. Who skips it buries. Do not forget this.

Sharing is solved with marketplaces. Curated plugin collections sit in repositories. They install with a single command. A marketplace joins from GitHub or another source. Even the command name is known. Then you browse and install from the built-in menu. Community marketplaces are already emerging. Dan Avila published operations and docs plugins. Seth Hobson gathered more than 80 specialist sub-agents. Samples are ready too. Pull request reviews, security guidance, and SDK work. Setup is no longer the problem. Choosing is. The command is short. The menu is near. The choice is yours. ^{[3] [4]}

The numbers whet appetites too. Claude Code launched in May 2025. Its run-rate revenue passed 500 million dollars. It grew tenfold in three months. Enterprise developers embraced the product. The company overall reached a 5 billion dollar pace. A 13 billion dollar Series F stands behind it. The growth is real. But growth and maintenance are not the same thing. Where money arrives, order must arrive too. Otherwise every team builds its own marketplace. Then nobody understands anyone else's. Growth grows the team. Maintenance keeps it alive. They are separate jobs. ^{[5] [6]}

A single agent has two ceilings. Context windows are finite. Even millions of tokens are not free. One session cannot wear many hats. Architect, test author, and documenter do not fit at once. Sub-agents give three wins. Context isolation arrives. Each one sees only what it needs. Parallelism arrives. Independent jobs run together. Wall-clock time shrinks by one over N. Role specialization arrives. Each sub-agent gets its own skill, model, and hook. Model choice is written too. The frequently born run on Haiku. The main coordinator runs on Sonnet. Deep one-shot jobs run on Opus, then stop. Stopping is design too. ^{[6] [7]}

Let me write the counter-view too. Excess modularity breeds trouble of its own. A separate plugin per job means a separate version per plugin. Which of eighty sub-agents is current. Which is safe. Who audited it. As the marketplace grows, so grows the junk. Sometimes a single-file setup is more honest. Fewer parts mean fewer failures. Modularity is not free. The maintenance calendar pays its price. A team with no such calendar should not enter the marketplace. Ledger first, plugin later. Do not reverse this.

Let me end with an open question. Which of these marketplaces lives six months from now. Which turns into an abandoned depot. My watched measures are set. Not plugin counts, but update dates. Not star counts, but review records. I ask my team and myself the same question. Does the plugin you built live without you. If the answer is no, do not build it. If yes, write it, explain it, share it. What lasts is not the plugin but the maintenance habit. Write this on the wall. Read it every Monday. Report when the answer changes.