Skip to content
Back to skills

Spawn New Session

ASecurity

Hand work to Claude agents in their own cmux tabs.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsgogit

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 29, 2026

npx -y skills add Pawel-Kica/claude-code-100 --skill spawn-new-session --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Spawn New Session?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Spawn New Session
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/pawel-kica-spawn-new-session/badge)](https://www.skillsdirectory.com/skills/pawel-kica-spawn-new-session)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: spawn-new-session
description: Hand work to Claude agents in their own cmux tabs.
argument-hint: "[task, or several tasks to split across agents]"
---

Peer agents, not subagents: full Claude sessions in their own cmux tabs, each with its own context and permissions, user watching.

## Run

1. Write a brief per agent to `~/.claude/spawns/<YYYY-MM-DD-HHMM>-<slug>.md`. It is the whole handoff — the tab inherits nothing from this conversation.
2. `~/.claude/skills/spawn-new-session/scripts/spawn-agent.sh --brief <path> --cwd <dir> --label <slug>`. `--cwd` = current working dir unless the task clearly belongs elsewhere. Always spawn in background — never pass `--focus true`, even if the user says they will watch; they switch tabs themselves. `--split` for a pane, `--prompt <text>` to override the default kickoff prompt. cmux only — exits 3 if the cmux socket is unreachable.
3. `cmux read-screen --surface <ref> --lines 30` — expect the Claude TUI.
4. Report a table: Task | Tab | Brief. Then stop — the tabs own that work now.

## Brief

```markdown
# <title>
## Objective — done, in a line
## Context — decisions already made and why, constraints, gotchas; specs/PRs by path or URL
## Where — cwd, key files
## Do — ordered steps
## Goal / Done When — checkable criteria
## Suggested skills — /<skill>, why
```

A brief that ends in `git commit`/`push` says in writing that user approves first.

Files in this skill

  • SKILL.md1.4 KB
  • scripts/spawn-agent.sh3.6 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…