spawn

A command for starting another Claude Code session in a terminal tab, an editor, or a headless process that runs without an interactive screen.

In plain words
What is it for?
Use it to start interactive, prompt-driven, headless, or VS Code sessions, optionally choosing a project path and model.
Why use it?
It lets you launch work in a chosen project and mode without manually setting up each new session.

Command

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add commands/tdimino/claude-code-minoan/spawn
Clone the repo
git clone --depth 1 https://github.com/tdimino/claude-code-minoan
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 184 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00184
Opus 5 $0.00000 $0.00092
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00018

Measured 3d ago against content hash 889a64b24431, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spawn scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/spawn.md · 28 lines

What it actually says

Spawn Session

Start a new Claude Code session in a terminal tab or run a headless prompt.

Arguments

$ARGUMENTS

Instructions

Run the new-session script with the provided arguments:

~/.claude/skills/claude-tracker-suite/scripts/new-session.sh $ARGUMENTS

If no project path is given, use the current working directory.

Examples:

  • /spawn ~/my-project — Interactive session in Ghostty
  • /spawn ~/my-project --prompt "fix the tests" — Prompt-driven in Ghostty tab
  • /spawn ~/my-project --headless --prompt "summarize" — Headless JSON output
  • /spawn ~/my-project --vscode --model opus — Interactive in VS Code
Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 28 lines · 0 tokens per session scan A 889a64b24431

Subscribe to this mod's changes

spawn is a command published in the GitHub repository tdimino/claude-code-minoan (41 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 184 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.