Kerinin Claude Modes
kerinin-claude-modes is a Claude Code plugin for the Build phase that enforces modal execution by limiting agent actions according to the active workflow mode.
by kerinin · github.com/kerinin/claude-modes
Enforce modal execution modes in Claude Code so the agent stays in workflow-appropriate actions instead of drifting across unrestricted tool use.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install kerinin-claude-modes@kerinin/claude-modesBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:kerinin/claude-modes") and the paste-ready config with skillselion.get_install_config("plugin:kerinin/claude-modes").
What it does
kerinin-claude-modes is a Claude Code plugin that introduces modal execution: you pick or switch modes and the runtime enforces which classes of actions are allowed in that context. Solo builders juggling build, review, and hotfix sessions benefit because the same agent can feel too powerful without guardrails—one mistaken bash or broad refactor can erase an afternoon. This plugin sits in development-oriented discovery but functions as a cross-cutting workflow control. Install it when you already rely on Claude Code for multi-step rituals and want explicit mode boundaries rather than hopeful prompting. It complements skills and MCP servers by governing how tools fire, not which API you call. Expect to configure modes to match your house rules; the value is consistent enforcement session to session, especially when you alternate between creative build work and cautious ship-phase review.
Highlights
- Modal execution plugin: distinct modes for different Claude Code workflows
- Enforces action limits based on the current active mode
- Keywords surface modes, workflows, enforce, and limiting behaviors
- Single-plugin bundle focused on development-category agent discipline
- Helps prevent scope creep when the agent would otherwise take unrestricted actions
Why builders use it
Unrestricted agent sessions make it easy for Claude Code to take actions that fit the wrong phase of your solo-builder workflow.
With modes enabled, each session respects enforced action boundaries so build, review, and iteration work stay intentionally scoped.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 0 stars, 0 votes.
FAQ
Who is kerinin-claude-modes for?
Solo builders and small teams who use Claude Code for structured workflows and want enforced limits on agent actions per mode.
When should I use kerinin-claude-modes?
Use it when switching between implementation, review, and ops-style tasks and you need the agent to respect different action rules in each context.
How do I add kerinin-claude-modes to my agent?
Install the plugin from the kerinin/claude-modes repository into Claude Code, enable it in your plugin list, and configure the modes documented in the repo README.
Comments
Share how you use kerinin-claude-modes, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.