sessions-spawn

Spawn sub-agent sessions with contracts and scoped access.

6|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/Acosmi/CrabClaw --skill sessions-spawn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sessions-spawn
Source: https://github.com/Acosmi/CrabClaw/tree/main/docs/skills/tools/sessions/sessions-spawn
Command: npx skills add https://github.com/Acosmi/CrabClaw --skill sessions-spawn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spawn sub-agents and enforce scoped contracts to enable safe, delegated task execution within a sandboxed environment.

Core Features & Use Cases

  • Create coder, media, or custom agent sessions with initial prompts
  • Enforce contracts, scope checks, and isolation for safe delegation
  • Support plan_confirm approval workflow and multi-agent coordination

Quick Start

Spawn a new session for a chosen agent with an initial prompt and a defined scope.

Frequently Asked Questions about sessions-spawn

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a scoped contract for sub-agent delegation?

A scoped contract restricts a sub-agent's execution boundaries by enforcing access controls and isolation rules within a sandboxed environment. This mechanism ensures delegated tasks operate securely without exceeding their defined permissions or compromising the parent workflow.

How do I spawn a sub-agent session with an initial prompt?

You spawn a sub-agent session by selecting an agent type—such as coder, media, or custom—and providing an initial prompt alongside a defined scope. This initiates task delegation within a sandboxed workflow governed by plan_confirm approvals.

Can I use custom agents for multi-agent coordination?

Yes, custom agent sessions support multi-agent coordination by allowing multiple spawned sub-agents to operate within scoped contracts. Each agent executes its delegated tasks in an isolated sandbox while adhering to the defined security level and plan_confirm workflow.

Does sandbox isolation enforce security levels for spawned sessions?

Sandbox isolation enforces security levels by applying scope checks and agent contracts to spawned sessions. This ensures consistent, secure execution that aligns with min_tier requirements, wizard_group specifications, and the designated security_level configuration.

What is the plan_confirm approval workflow for delegated tasks?

The plan_confirm approval workflow acts as a checkpoint for delegated tasks within a sandboxed execution environment. It requires validation before a sub-agent proceeds, ensuring that scoped contracts and security constraints are verified prior to action.