Kerinin Claude Modes
- Updated January 12, 2026
- kerinin/claude-modes
kerinin-claude-modes is a Claude Code plugin that enforces modal execution by limiting agent actions according to the active workflow mode.
About
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. developers 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 review.
- 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
Kerinin Claude Modes by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install kerinin-claude-modes@kerinin/claude-modesAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| Last updated | January 12, 2026 |
|---|---|
| Repository | kerinin/claude-modes ↗ |
What it does
Enforce modal execution modes in Claude Code so the agent stays in workflow-appropriate actions instead of drifting across unrestricted tool use.
Who is it for?
Best when you run repeatable Claude Code workflows and need hard guardrails on what the agent can do in each mode.
Skip if: Casual one-off chats where you want maximum agent freedom and no mode configuration overhead.
What you get
With modes enabled, each session respects enforced action boundaries so build, review, and iteration work stay intentionally scoped.
- Configurable modal execution profiles for Claude Code
- Enforced action limiting tied to the current mode
- More predictable agent behavior across build and review sessions
By the numbers
- pluginCount: 1
- categories: development
- pluginKeywords include: modes, workflows, enforce, limiting, actions
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Execution-policy plugin for Claude Code, not an MCP server integration or a domain-specific coding skill.
FAQ
Who is Kerinin Claude Modes for?
Developers 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.