Butler Mode
WarnAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill is transparent about delegation, but it tells the agent to launch teammates with unrestricted or bypassed permissions and direct coordination, so users should review and constrain it before use.
Install only if you intentionally want a multi-agent manager workflow. Before use, remove or avoid bypass-permission modes, require approval before spawning teammates, limit each agent's tools and file access, cap parallel agents, and keep inter-agent communication visible when working on sensitive repositories or accounts.
Findings (6)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
A teammate agent could edit files, run commands, or use other available tools with little containment if the user's environment exposes those tools.
This makes broad tool access the default for spawned agents instead of scoping tools to the user's specific task or requiring approvals for high-impact actions.
Always spawn agents with maximum autonomy and all available tools. Do not restrict what an agent can use or how it works.
Require explicit user approval before spawning agents, pass only the minimum needed tools/files, and avoid unrestricted delegation for sensitive projects.
Spawned agents may act with fewer permission prompts than the user expects, increasing the chance of unintended file or environment changes.
The Claude Code spawn example uses a permission-bypass mode, which can exceed normal approval boundaries for delegated work.
mode: "bypassPermissions"
Do not use bypass-permission modes by default; require task-specific approval and least-privilege execution for each teammate.
Project details or sensitive context could be shared among subagents without the user seeing or approving each exchange.
The skill encourages direct agent-to-agent coordination without defining message logging, identity checks, data boundaries, or user visibility.
Agents should coordinate directly — you don't need to relay every message
Keep inter-agent communication visible to the manager/user, define what data may be shared, and require escalation before sharing sensitive files or credentials.
Multiple agents could continue making changes or consuming resources beyond what the user expected for a single request.
The skill promotes parallel autonomous agents but does not define caps, timeouts, stopping conditions, or approval gates for additional spawned work.
Spawn multiple teammates in parallel when tasks are independent
Set a maximum number of agents, require user approval for new subagents, and enforce clear stop/kill conditions.
The agent may refuse or avoid doing direct work and instead create subagents even for tasks the user expected it to handle itself.
This intentionally changes the agent's normal behavior from doing work directly to delegating work; it is purpose-aligned but important for users to notice.
Your role is exclusively managerial. ... Delegate all substantive work to teammates.
Use this skill only when you explicitly want a manager/delegation workflow, and disable it for simple tasks that do not need subagents.
Users have less external context for verifying the publisher or reviewing the skill outside the registry.
The skill is instruction-only and has no install code, but the missing source/homepage limits provenance verification.
Source: unknown; Homepage: none
Verify the registry owner and read the full SKILL.md before enabling it.