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.
npx agentmods add skills/thobustos/openyoko/spawnnpx skills add ThoBustos/openyoko --skill spawngit clone --depth 1 https://github.com/ThoBustos/openyokoWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.02913 |
| Opus 5 | $0.00000 | $0.01456 |
| Sonnet 5 | $0.00000 | $0.00583 |
| Haiku 4.5 | $0.00000 | $0.00291 |
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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spawn Skill
Spin up a new Claude Code instance in a fresh tmux pane with full context handoff. Use this to delegate work to a parallel session, offload research, or start fresh with a synthesized plan.
Convention:
- Flow, tmux commands, handoff prompts
- Repo/vault paths come from arguments, current directory, or
config/vault.json(see CLAUDE.md)
Usage
/spawn # Interactive - asks for context
/spawn <repo-path> # Spawn in specific repo
/spawn <repo-path> "<prompt>" # Spawn with specific initial prompt
Philosophy
Context windows degrade. Fresh sessions are sharp. This skill lets you:
- Hand off a plan to a fresh instance for execution
- Spin up parallel research without polluting your main context
- Delegate a subtask while you continue working
- Start a new session with synthesized context from current work
The default first action for spawned sessions is review and validate - ensuring no discrepancies in the handed-off plan and enforcing best practices.
Flow
Phase 1: Preflight Checks
Check tmux is running:
if [ -z "$TMUX" ]; then
echo "ERROR: Not inside a tmux session"
exit 1
fi
If not in tmux → STOP and tell user: "You must be inside a tmux session to use /spawn. Run tmux first."
Get current window and pane info:
CURRENT_WINDOW=$(tmux display-message -p '#I')
CURRENT_PANE=$(tmux display-message -p '#P')
Phase 2: Gather Context
If no arguments provided, ask:
-
Target repo path - Where should the new Claude Code run?
- Default: current working directory (
$(pwd)) - Options: current workspace, vault (from
config/vault.json), or another path the user specifies
- Default: current working directory (
-
Initial prompt - What should the new instance do first?
- Default: "Review the current plan and ensure no discrepancies. Validate approach against best practices before proceeding."
- Custom: User provides specific instructions
-
Context to hand off (optional):
- Current plan/iteration being discussed
- Key files to read first
- Specific constraints or decisions made
- Skills to invoke (e.g.,
/daily,/scan)
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.
- 2d ago First seen · 396 lines · 0 tokens per session scan A 5a7b789c63e1
spawn is a skill published in the GitHub repository ThoBustos/openyoko (10 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,913 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…