Claude Toolbox

Name: Claude Toolbox
Author: moxer-mmh

moxer-mmh/claude-toolbox·2 plugins

Install moxer-mmh’s toolbox for lean subagents that trim MCP schema bloat and worktree-guard git safety for multi-agent Claude sessions.

Overview

claude-toolbox is a plugin marketplace for the Build phase that provides lean-agents for MCP-aware subagents and worktree-guard for safe multi-agent git worktrees.

What is this marketplace?

2 plugins: lean-agents v1.0.0 (MIT) and worktree-guard v1.0.0 (MIT)
lean-agents: lightweight subagents avoiding inherited MCP tool schema bloat; Sonnet filtered tools and Opus safe 1M cont
worktree-guard: git worktree safety hooks for multi-agent workflows
Tagged themes: agents, mcp-workaround, worktree, safety-guards, performance
Repository hub: github.com/moxer-mmh/lean-agents
2 plugins in marketplace.json
Both plugins version 1.0.0 MIT license
lean-agents homepage and repository on github.com/moxer-mmh/lean-agents

Compatible agents: Claude Code, Cursor, Codex

Community signal: 1 GitHub stars.

What problem does it solve?

Multi-agent Claude Code setups bloat context with MCP schemas and risk corrupted repos without worktree isolation.

Who is it for?

Solo builders running multiple Claude agents on one codebase who hit MCP context limits or git collisions.

Skip if: Casual single-thread coding with no subagents, worktrees, or MCP servers.

What do I get? / Deliverables

After registration, you get lean subagent profiles with tool filtering plus worktree safety hooks for parallel agent development.

lean-agents plugin with filtered Sonnet and Opus safe variants
worktree-guard plugin with safety hooks for multi-agent git use

Plugins in this marketplace

2 plugins — install individually after you add the marketplace.

PluginVersion

Lean AgentsLightweight subagent replacements that avoid context bloat from inherited MCP tool schemas. Provides Sonnet variants with tool filtering and Opus safe variants with 1M context.1.0.0 Worktree GuardAutomatic safety guards for git worktrees: blocks bad pushes, wrong branches, and provides safe sync/push/status commands. Essential for multi-agent workflows with one agent per worktree.1.0.0

Recommended Marketplaces

1NoBeef1 Marketplace1NoBeef1/1NoBeef1-marketplace

1NoBeef1-marketplace is a minimal Claude Code plugin marketplace shipping one personality plugin, rocky-mode, inspired b…7 stars

3 Surgeons Marketplacesupportersimulator/3-surgeons

3-surgeons-marketplace is a Claude Code plugin marketplace that ships one plugin, 3-surgeons, bundling twenty-one skills…2 stars

A5c.Aia5c-ai/babysitter-claude

a5c.ai is a Claude Code marketplace that distributes babysitter, an orchestration plugin for complex, multi-step workflo…

Aevccaevelop/aevcc

aevcc is Aevelop's Claude Code marketplace packaging one workflow-oriented plugin that aggregates patterns solo builders…

Agent Engineering Toolkitrodrigorjsf/agent-engineering-toolkit

agent-engineering-toolkit is rodrigorjsf’s Claude Code marketplace bundling three developer-tools plugins for serious ag…

Agentheimheimeshoff/Agentheim

agentheim is a one-plugin Claude marketplace packaging an DDD-flavored agentic harness: Socratic vision modeling, bounde…23 stars

Journey fit

Primary fit

BuildAgent skills & templates

Build / agent-tooling is primary because lean-agents directly optimizes subagent context and MCP tool filtering during development. agent-tooling captures Sonnet tool-filter variants, Opus 1M safe variants, and worktree guards aimed at parallel agent work on one repo.

How it compares

Agent performance and git-safety marketplace, not a planning or certificate workflow pack.

Common Questions / FAQ

Who is Claude Toolbox for?

Advanced Claude Code users orchestrating subagents with MCP who need leaner context and safer git worktrees.

When should I use Claude Toolbox?

Use it when MCP tool schemas slow sessions or when you run parallel agents that should use separate worktrees.

How do I add Claude Toolbox to my agent?

Add market:moxer-mmh/Claude Toolbox, install lean-agents and worktree-guard plugins, enable hooks, and configure worktrees in your repo.