Claude Code Mods and the Side Agent: What a Solo Dev Enables

Claude Code shipped five developer-facing changes between 1 and 6 October 2026, and a solo developer should switch on two of them today. Version 2.1.287 on 1 October added Claude Mods and a built-in mod called You should know. Version 2.1.292 on 6 October added an effort parameter to the Agent tool, a --marketplace flag on plugin install and a new retry-delay environment variable for 529 overload errors. Versions 2.1.293 and 2.1.294 followed on 7 and 8 October.

Short answer: turn on the Agent-tool effort habit immediately, because it costs nothing and cuts the bill on mechanical sub-agent work. Trial the You should know side agent on one repository for a week. Set the 529 backoff variable only if you actually see overload errors. Ignore --marketplace until you distribute plugins to a team, and read about Mods before you write one. Everything below comes from the official changelog at code.claude.com/docs/en/changelog unless a line says "reported".

What Claude Mods change

Until 2.1.287, a plugin could add commands, skills, hooks and agents around Claude Code. The changelog entry for that release reads: "Added Claude Mods: plugins may now modify deeper behavior." The word that matters is deeper. A mod is a plugin that reaches into parts of the product that used to be fixed.

The proof is in what already shipped as one. Some built-in features now arrive as mods, and the changelog uses /diff as the example: you can disable it in /plugin or replace it with your own. That is a change of ownership. A built-in command stops being a fixed feature and becomes a default you can swap, the same way you swap an editor extension.

Two mod APIs landed in 2.1.292 and show the direction. prompt.autocomplete lets a mod shape what the prompt box suggests. $.tool.register registers a tool, and it accepts an isDeferred option, so a mod can add a tool without paying its schema cost in every request until Claude needs it. If you have watched your context fill with tool definitions you never call, deferred registration is the part to care about.

The catch: Mods raise the trust bar. A plugin that only adds a slash command can do limited damage. A plugin that modifies core behaviour sits in the path of everything you type and every tool call Claude makes. Install mods from sources you can read, pin versions, and keep your plugin list short. The same rule applies to the new --marketplace flag, covered below.

For a solo developer the practical takeaway is narrow. You do not need to write a mod this month. You do need to know that "Claude Code behaves like this" is now sometimes "my installed plugins make it behave like this", which matters the next time a teammate's session acts differently from yours. When you debug odd behaviour, open /plugin first.

The You should know side agent

You should know is the first built-in mod, and it is the one most people will try. The 2.1.287 changelog describes it as a side agent that watches your back and flags things you or Claude might miss. It runs alongside the main session rather than inside it, so its job is the opposite of the main agent's job: it is not trying to finish your task, it is looking for what the task is about to break.

The changelog gives the exact enable command, and notes it applies to first-party sessions with telemetry on:

/plugin enable cc-plugin-you-should-know@builtin

That condition is easy to miss. If you run Claude Code through a third-party cloud provider or you have telemetry switched off, the mod may not be available to you. Check before you assume it is broken.

Version 2.1.288 on 2 October changed the wording of its notes so they say "we", "the main agent" or "you" depending on who is responsible for the thing flagged. That sounds cosmetic and is not. A flag that says "you" asks you to act. A flag that says "the main agent" tells you Claude should fix it and you can leave it alone. Version 2.1.290 on 5 October fixed a bug where it wrote English regardless of your configured language setting. Two fixes in four days tells you the feature is young.

How I would trial it

Pick one repository with real tests and a CLAUDE.md you trust. Enable the mod, then work normally for five working days. Keep a plain text file open and add a line each time a flag was useful, ignorable or wrong. At the end of the week you have three numbers and a decision. If useful flags outnumber wrong ones, keep it. If it nags you about things your hooks already catch, switch it off with /plugin.

One cost question stays open. The changelog does not state how many tokens the side agent consumes, and a second agent watching a session is not free. Watch your usage numbers during the trial week rather than guessing. If you are running agents at volume, the Prompt Bloat Analyzer, new today, shows how much of each request your standing instructions consume, which is the part every extra agent pays again.