원클릭으로 Manus에서 모든 스킬 실행

spawn-agent

스타3

포크0

업데이트2026년 7월 16일 21:15

Spawn a new coding-agent CLI session (Claude Code, and other agents as they are added) in a background tmux pane, in auto-approve/skip-permissions mode, enabling remote control for agents that support it and returning the shareable session link. Use when the user asks to launch/create another agent session in tmux, start a background agent, or spin up a remote-controllable Claude/agent session.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

glebglazov

glebglazov/dotfiles

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Agent registry

Each supported agent defines how to launch it and whether it has a remote-control link. Only add an agent here once its flags are verified.

Agent	Keyword(s)	Launch command	Skip-perms flag	Title rewrite	Remote control
Claude Code	`claude` (default)	`claude --dangerously-skip-permissions`	(part of launch)	→ `✳ Claude Code`	`/remote-control` slash command → prints `https://claude.ai/code/session_...`

If the user names an agent not in this table, tell them it isn't supported yet (and that the table is where to add it) rather than guessing flags.

Parsing arguments

Arguments are optional and free-form. Extract:

Agent name — matches a keyword in the registry. Defaults to claude if absent.
A target directory — a path (~/Dev/foo, ../bar, absolute). If none, use the current directory/session. Expand ~/relative to absolute and confirm it exists (ls -d <path>) before spawning.
An initial prompt — remaining text to type into the new session once it's up.

Steps

Verify you are inside tmux. Run echo "$TMUX". If empty, tell the user this skill requires an active tmux session and stop.
Resolve the agent from the registry — its launch command, whether it has remote control, and how its title is rewritten.
Spawn the pane. Use pop pane (tmux-pane skill wrapper). Give the pane a name derived from the agent (claude-spawn, codex-spawn, …). Capture the pane id from stdout — you need it because most agents rewrite the pane title on launch, which breaks name-based lookup.
```
PANE_ID=$(pop pane create <agent>-spawn "<launch command>")
echo "PANE_ID=$PANE_ID"
```
If the user named a target directory, add --project <abs-path> so the pane spawns in that project's tmux session and starts the agent there:
```
PANE_ID=$(pop pane create <agent>-spawn "<launch command>" --project <abs-path>)
```
The tmux session is auto-created if it doesn't exist. Pane ids are global across the tmux server, so later tmux ... -t "$PANE_ID" commands work regardless of which session the pane lives in.
Wait for startup. direnv and agent boot take a few seconds. Sleep ~4s, then confirm the prompt is ready:
```
sleep 4; tmux capture-pane -p -t "$PANE_ID" | grep -v '^$' | tail -20
```
Look for the agent's banner and input line. If not ready, sleep and re-capture.
Enable remote control — only if the agent supports it. For Claude, send the slash command, wait, then capture the link:
```
tmux send-keys -t "$PANE_ID" "/remote-control" Enter
sleep 3; tmux capture-pane -p -t "$PANE_ID" | grep -v '^$' | tail -20
```
Extract the session URL from the output. For agents with no remote control, skip this step.
(Optional) Send an initial prompt. If the user passed one, type it into the pane after any remote-control step:
```
tmux send-keys -t "$PANE_ID" "<the prompt>" Enter
```
Report back: the agent, pane id, session directory, mode (skip-permissions), and the remote-control link (or note that this agent has none). Warn about anything the startup capture flagged (e.g. Claude MCP servers needing auth → run /mcp in that pane).

Notes

Always target the pane by id ($PANE_ID), not by name — agents that rewrite the pane title break pop pane capture <name> / find after startup.
To spawn several at once, loop over the requested agents/dirs with distinct pane names (claude-spawn, claude-spawn-2, …). pop pane create is idempotent per name and auto-recreates a dead pane. Report each spawned session.
To add a new agent: verify its auto-approve flag and any remote-control command in a throwaway pane first, then add a registry row. Keep this skill honest — never list an agent whose flags you haven't confirmed.

이 저장소의 다른 Skills

같은 저장소

run-task

glebglazov/dotfiles

Pick and implement exactly one task from a to-tasks manifest (index.json). Explicit invocation only — use when the user types /run_task (Cursor) or $run-task (Codex) with a task-set folder.

2026-06-273

tdg-task-commit

glebglazov/dotfiles

Turn conversation work into a git commit for Tripledot backend repos' [TASK] PR→JIRA GitHub Action (`maybe_create_jira_task_from_pr`). Use when the user wants to commit changes AND auto-create a JIRA task — e.g. "commit this and create a jira task", "make a [TASK] commit", "commit this for jira", "wrap this up as a task", or any [TASK] automation reference; also when they say "commit this as a task" without naming JIRA. Reads the workflow for the target project, matches house Story format, writes the commit body in JIRA wiki markup (not Markdown). Only for repos that ship this automation. Stay DORMANT if the branch already has a ticket key (e.g. GS-1234-...), commits ahead of base, or an open PR — the Action uses the FIRST commit only; later [TASK] commits noop or duplicate. For fresh branches where the [TASK] commit is first.

2026-06-273

name	spawn-agent
description	Spawn a new coding-agent CLI session (Claude Code, and other agents as they are added) in a background tmux pane, in auto-approve/skip-permissions mode, enabling remote control for agents that support it and returning the shareable session link. Use when the user asks to launch/create another agent session in tmux, start a background agent, or spin up a remote-controllable Claude/agent session.
argument-hint	Optional: agent name (default claude), a directory to start in, and/or an initial prompt

Agent registry

Each supported agent defines how to launch it and whether it has a remote-control link. Only add an agent here once its flags are verified.

Agent	Keyword(s)	Launch command	Skip-perms flag	Title rewrite	Remote control
Claude Code	`claude` (default)	`claude --dangerously-skip-permissions`	(part of launch)	→ `✳ Claude Code`	`/remote-control` slash command → prints `https://claude.ai/code/session_...`

If the user names an agent not in this table, tell them it isn't supported yet (and that the table is where to add it) rather than guessing flags.

Parsing arguments

Arguments are optional and free-form. Extract:

Agent name — matches a keyword in the registry. Defaults to claude if absent.
A target directory — a path (~/Dev/foo, ../bar, absolute). If none, use the current directory/session. Expand ~/relative to absolute and confirm it exists (ls -d <path>) before spawning.
An initial prompt — remaining text to type into the new session once it's up.

Steps

Verify you are inside tmux. Run echo "$TMUX". If empty, tell the user this skill requires an active tmux session and stop.
Resolve the agent from the registry — its launch command, whether it has remote control, and how its title is rewritten.
Spawn the pane. Use pop pane (tmux-pane skill wrapper). Give the pane a name derived from the agent (claude-spawn, codex-spawn, …). Capture the pane id from stdout — you need it because most agents rewrite the pane title on launch, which breaks name-based lookup.
```
PANE_ID=$(pop pane create <agent>-spawn "<launch command>")
echo "PANE_ID=$PANE_ID"
```
If the user named a target directory, add --project <abs-path> so the pane spawns in that project's tmux session and starts the agent there:
```
PANE_ID=$(pop pane create <agent>-spawn "<launch command>" --project <abs-path>)
```
The tmux session is auto-created if it doesn't exist. Pane ids are global across the tmux server, so later tmux ... -t "$PANE_ID" commands work regardless of which session the pane lives in.
Wait for startup. direnv and agent boot take a few seconds. Sleep ~4s, then confirm the prompt is ready:
```
sleep 4; tmux capture-pane -p -t "$PANE_ID" | grep -v '^$' | tail -20
```
Look for the agent's banner and input line. If not ready, sleep and re-capture.
Enable remote control — only if the agent supports it. For Claude, send the slash command, wait, then capture the link:
```
tmux send-keys -t "$PANE_ID" "/remote-control" Enter
sleep 3; tmux capture-pane -p -t "$PANE_ID" | grep -v '^$' | tail -20
```
Extract the session URL from the output. For agents with no remote control, skip this step.
(Optional) Send an initial prompt. If the user passed one, type it into the pane after any remote-control step:
```
tmux send-keys -t "$PANE_ID" "<the prompt>" Enter
```
Report back: the agent, pane id, session directory, mode (skip-permissions), and the remote-control link (or note that this agent has none). Warn about anything the startup capture flagged (e.g. Claude MCP servers needing auth → run /mcp in that pane).

Notes

Always target the pane by id ($PANE_ID), not by name — agents that rewrite the pane title break pop pane capture <name> / find after startup.
To spawn several at once, loop over the requested agents/dirs with distinct pane names (claude-spawn, claude-spawn-2, …). pop pane create is idempotent per name and auto-recreates a dead pane. Report each spawned session.
To add a new agent: verify its auto-approve flag and any remote-control command in a throwaway pane first, then add a registry row. Keep this skill honest — never list an agent whose flags you haven't confirmed.