Spawn
Launch N parallel subagents in isolated git worktrees to compete on the session task.
Before & after
Same prompt, same agent — the only difference is the skill.
I can help you explore different authentication approaches. You could try a few different strategies and see which one works best for your use case. Some teams use OAuth, others use JWT, and some still use sessions. Each has pros and cons depending on your requirements. What kind of API are you building, and how many users do you expect? That would help me suggest the best approach to explore.
SPAWN CONFIGURATION: Auth Architecture Competition AGENT 1: Session-Based Auth (Baseline) • Isolated worktree: auth-session-baseline • Task: Implement Express middleware for HTTP-only cookie sessions; Redis-backed store; CSRF tokens on POST • Deliverable: Runnable server + integration test suite • Target metrics: Time-to-auth <50ms, session memory per user <200 bytes AGENT 2: JWT Stateless Auth (Challenge A) • Isolated worktree: auth-jwt-stateless • Task: Implement JWT issuance/verification; refresh token rotation; revocation via blacklist cache (Redis) • Deliverable: Same test suite (no framework changes, same API contracts) • Success criteria: Faster initial auth vs Agent 1, but measure refresh overhead AGENT 3: OAuth 2.0 Delegated (Challenge B) • Isolated worktree: auth-oauth-delegated • Task: Integrate with provider; handle scope negotiation, consent screen, callback verification • Deliverable: Drop-in SDK; same test pass rate as Agent 1/2 • Trade-off focus: User experience (consent flow friction) vs zero password storage EVALUATION CRITERIA (all agents benchmarked identically) ✓ Test suite pass rate (baseline: 98%+) ✓ Auth latency p95 (target: <75ms) ✓ Code complexity (cyclomatic complexity per method <8) ✓ Security audit: CVE exposure (0 known vulnerabilities) ✓ Scaling load: 1000 concurrent sessions (memory growth rate) JUDGMENT CALL No winner chosen by default. Each branch merges to feature branches; final choice depends on downstream requirements (mobile vs web, user base size, operational maturity).
About this skill
name: spawn description: Use when Launch N parallel subagents in isolated git worktrees to compete on the session task.
Spawn
Launch N parallel subagents in isolated git worktrees to compete on the session task. Use when the user runs /hub:spawn or asks to start the competing agents for an initialized AgentHub session.
What you get
- Public GitHub repo (alirezarezvani/claude-skills)
- the spawn skill folder with SKILL.md. Part of a 337-skill / 30-agent / 70-command install.
Customize your output
- Fork the repo and adapt the skill's instructions and references to your workflow.
Example output
Activates automatically when your request matches Spawn; chains with the other skills, agents, and commands in the collection.
Best for
Creators, builders, and teams using Claude Code.
SKILL.md preview
---
name: spawn
description: Use this skill when the user runs /hub:spawn or asks to launch competing subagents in isolated git worktrees for an initialized AgentHub session.
version: 1.0.0
category: Development / Engineering
author: AgentVolt
license: proprietary
tags:
- development
- engineering
---
# Spawn
Launches N parallel subagents, each in its own isolated git worktree, to independently attempt the current session's task so their results can be compared.
## When to use
… (sign up to view the full skill)More development skills
View all Development skills →Generate
Scaffold code, tests, and boilerplate from a short spec.
Performance Profiler
Systematic performance profiling for Node.js, Python, and Go applications.
Threat Detection
Use when hunting for threats in an environment, analyzing IOCs, or detecting behavioral anomalies in telemetry.
Agent Harness
Turns a domain folder of skills into a bounded agentic loop: compile a goal into a task plan, execute with the domain's tools, verify every task, retry within a budget.