Paseo Advisor Second Opinion
getpaseo/paseo
Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.
A skill your agent uses when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation.
Install Team Orchestrator
$ npx skills add sangrokjung/claude-forge --skill team-orchestrator -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install sangrokjung/claude-forge team-orchestrator --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/team-orchestrator .claude/skills/team-orchestrator && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "team-orchestrator" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestrator into .claude/skills/team-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-orchestrator", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestratorType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add sangrokjung/claude-forge --skill team-orchestrator -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install sangrokjung/claude-forge team-orchestrator --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/team-orchestrator .agents/skills/team-orchestrator && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-orchestrator" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestrator into .agents/skills/team-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-orchestrator", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sangrokjung/claude-forge --skill team-orchestrator -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install sangrokjung/claude-forge team-orchestrator --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/team-orchestrator .cursor/skills/team-orchestrator && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "team-orchestrator" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestrator into .cursor/skills/team-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-orchestrator", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/sangrokjung/claude-forge.git --path skills/team-orchestrator--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add sangrokjung/claude-forge --skill team-orchestrator -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install sangrokjung/claude-forge team-orchestrator --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/team-orchestrator .gemini/skills/team-orchestrator && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "team-orchestrator" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestrator into .gemini/skills/team-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-orchestrator", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install sangrokjung/claude-forge team-orchestratorInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add sangrokjung/claude-forge --skill team-orchestrator -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/team-orchestrator .github/skills/team-orchestrator && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "team-orchestrator" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestrator into .github/skills/team-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-orchestrator", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add sangrokjung/claude-forge --skill team-orchestrator -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install sangrokjung/claude-forge team-orchestrator --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/sangrokjung/claude-forge.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/team-orchestrator .opencode/skills/team-orchestrator && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "team-orchestrator" agent skill from https://github.com/sangrokjung/claude-forge/tree/main/skills/team-orchestrator into .opencode/skills/team-orchestrator/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-orchestrator", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
team-orchestrator- GitHub stars
- 852
- Token cost
- ~1.2k tokens
- SKILL.md length
- 389 words
- Files
- 1
- Skills in repo
- 24
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation.
- Works in 5 steps: 분석 단계 → 팀 구성 단계 → Task 생성 단계 → …
- Orchestrating Agent Teams for parallel development - team composition
- SKILL.md covers Overview, 전제조건, Team Composition and Task Distribution, plus 6 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Team Orchestrator is an agent skill from sangrokjung/claude-forge. Use when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation. Triggers on /orchestrate, multi-agent coordination, parallel team work, task delegation to teammates.
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Dependency management, Subagents and Multi-agent orchestration. The repository describes itself as: oh-my-zsh for Claude Code — 16 agents, 35 commands, 32 skills, 21 safety hooks in one install. v4.0 adds an adversarial review loop: a second agent that never sees the first… The licence is MIT.
When your agent uses it
- Orchestrating Agent Teams for parallel development - team composition
- Task distribution
- Dependency management
- Result aggregation
Example prompts
- “/team-orchestrator”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 34d881d. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Team Orchestrator loads about 1.2k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 389 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from sangrokjung/claude-forge at commit 34d881d, republished under its MIT licence (© sangrokjung). 389 words, ~1,230 tokens.
Download SKILL.mdSave it as
.claude/skills/team-orchestrator/SKILL.md (or your agent's skills folder).- name
- team-orchestrator
- description
- Use when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation. Triggers on /orchestrate, multi-agent coordination, parallel team work, task delegation to teammates.
- version
- 1.1.0
Overview
team-orchestrator 스킬은 /orchestrate 커맨드의 핵심 엔진으로,
Agent Teams를 구성하고 작업을 분배하며 결과를 집계하는 오케스트레이션 로직을 정의한다.
전제조건
Agent Teams 전제조건(환경변수 설정)은 reference/agents-teams-ref.md 참조.
Team Composition
팀 크기 결정
최대 팀원 수: Lead 1 + Teammates 3 (총 4명)
| 작업 규모 | 팀원 수 | 구성 |
|---|---|---|
| 소 (파일 1-3개) | 1-2명 | 구현1 (+테스트1) |
| 중 (파일 4-8개) | 2-3명 | 구현1-2 + 테스트1 |
| 대 (파일 9개 이상) | 3명 | 구현2 + 테스트1 또는 패턴별 분리 |
역할 템플릿
풀스택 기능 구현:
| 역할 | subagent_type | 담당 |
|---|---|---|
| Frontend Dev | general-purpose | UI 구현, 컴포넌트 |
| Backend Dev | general-purpose | API, DB, 로직 |
| QA Engineer | general-purpose | 테스트, E2E |
리팩토링:
| 역할 | subagent_type | 담당 |
|---|---|---|
| Analyzer | Explore | 코드 분석/계획 |
| Implementer | general-purpose | 리팩토링 실행 |
| Verifier | general-purpose | 테스트/검증 |
버그 조사:
| 역할 | subagent_type | 담당 |
|---|---|---|
| Investigator 1 | Explore | 코드 분석 |
| Investigator 2 | Explore | 로그/환경 분석 |
| Fixer | general-purpose | 수정 구현 |
Task Distribution
파일 소유권 분리 (CRITICAL)
같은 파일을 2명이 편집하면 덮어쓰기가 발생한다. 반드시 팀원별로 파일 소유권을 분리한다.
파일 소유권 결정 로직:
1. 변경 예상 파일 목록 생성
2. 파일별 모듈/도메인 분류
3. 도메인 단위로 팀원 배정
4. 공유 파일(types, config)은 한 팀원에게 독점 배정작업 분해 규칙
팀원당 5-6개 Task를 배정한다.
| Task 크기 | 판단 기준 | 설명 |
|---|---|---|
| 너무 작음 | 조율 오버헤드 > 이점 | 하나로 합치기 |
| 적절함 | 명확한 결과물이 있는 자체 포함 단위 | 함수, 테스트 파일, 검토 |
| 너무 큼 | 체크인 없이 오래 작동 | 더 작게 분할 |
의존성 관리
의존성 그래프 생성:
Task A (types 정의) → Task B (API 구현) → Task C (UI 연동)
선행 Task가 완료되어야 후행 Task 시작 가능
순환 의존성 감지 시 경고TaskCreate에서 addBlockedBy 필드로 의존성을 설정한다.
Context Inheritance (CRITICAL)
팀원은 프로젝트 컨텍스트(CLAUDE.md, MCP servers, skills)를 자동 로드하지만, 리더의 대화 기록은 상속하지 않는다.
따라서 팀원 생성 프롬프트에 반드시 다음을 포함해야 한다:
- 작업 목적과 배경
- 관련 파일 경로
- 기대하는 결과물
- 주의사항/제약사항
# 좋은 예시
"Review the authentication module at src/auth/ for security vulnerabilities.
Focus on token handling, session management, and input validation.
The app uses JWT tokens stored in httpOnly cookies."
# 나쁜 예시
"보안 검토 해줘" ← 팀원은 리더가 논의한 맥락을 모름CLAUDE.md는 정상 작동: 팀원들은 작업 디렉토리에서 CLAUDE.md를 자동으로 읽는다.
Show full SKILL.md (160 more words)Show less
Plan Approval Mode
위험하거나 복잡한 작업에서 팀원이 구현 전 계획 승인을 받도록 할 수 있다:
Spawn an architect teammate to refactor the auth module.
Require plan approval before they make any changes.동작:
- 팀원이 읽기 전용 계획 모드에서 시작
- 계획 완료 시 리더에게 plan_approval_request 발송
- 리더가 승인 → 팀원이 구현 시작
- 리더가 거부 (피드백 포함) → 팀원이 계획 수정 후 재제출
리더의 판단 기준을 프롬프트에 제공 가능:
- "테스트 커버리지를 포함하는 계획만 승인"
- "DB 스키마를 수정하는 계획 거부"
Execution Flow
1. 분석 단계
1. prompt_plan.md / spec.md 읽기
2. 변경 필요 파일 목록 생성
3. 파일별 도메인 분류
4. 작업 복잡도 추정2. 팀 구성 단계
1. 작업 규모에 따른 팀원 수 결정
2. 역할 템플릿 선택
3. 각 팀원에게 subagent_type 배정
4. 파일 소유권 분리3. Task 생성 단계
1. TaskCreate로 Task 목록 생성
2. 팀원별 5-6개 Task 배정
3. 의존성 설정 (addBlockedBy)
4. TaskUpdate로 owner 배정4. 실행 단계
1. 팀원 spawn (SendMessage)
2. 각 팀원이 자신의 Task 수행
3. 리더는 조율만 수행 (직접 구현 금지)
4. 팀원 완료 시 SendMessage로 보고4-1. 자체 청구 (Self-Claim)
작업을 마친 팀원은 다음 미할당, 차단되지 않은 작업을 자체적으로 선택한다. 작업 청구는 파일 잠금을 사용하여 경합 조건(race condition)을 방지한다.
5. 결과 집계 단계
1. 모든 팀원의 Task 완료 확인
2. 파일 충돌 여부 검증
3. 통합 빌드/테스트 실행
4. 결과 요약 생성Result Aggregation
성공 판단 기준
전체 성공 조건:
1. 모든 Task가 completed 상태
2. 빌드 성공
3. 타입 체크 통과
4. 테스트 통과부분 실패 처리
부분 실패 시:
1. 실패한 Task 식별
2. 실패 원인 분석 (의존성 문제, 파일 충돌 등)
3. 재배정 또는 리더가 직접 해결
4. 재시도 (최대 2회)집계 출력 형식
════════════════════════════════════════════════════════════════
Team Orchestration Result (v6)
════════════════════════════════════════════════════════════════
팀원: [N]명
총 Task: [N]개
완료: [N]개 | 실패: [N]개
팀원별 결과:
[역할 1]: [완료 Task 수]/[배정 Task 수] - [상태]
[역할 2]: [완료 Task 수]/[배정 Task 수] - [상태]
[역할 3]: [완료 Task 수]/[배정 Task 수] - [상태]
빌드: [PASS/FAIL]
타입: [PASS/FAIL]
테스트: [PASS/FAIL]
다음 단계:
/handoff-verify → /sync-docs → /commit-push-pr --merge --notify
(sync-docs는 머지 전 의무 — commit-push-pr v7이 게이트 내장)
════════════════════════════════════════════════════════════════Error Recovery
팀원 무응답
1. SendMessage로 상태 확인 (1회)
2. 5분 초과 시 Task 재배정
3. 필요시 새 팀원 생성파일 충돌 감지
1. 리더가 git status로 충돌 감지
2. 한 팀원에게 해당 파일 소유권 위임
3. 다른 팀원은 대기 후 진행Task 의존성 데드락
1. 순환 의존성 감지
2. 의존성 체인에서 가장 독립적인 Task 우선 실행
3. 리더가 수동으로 의존성 해소Integration
/orchestrate 연동
/orchestrate 커맨드가 이 스킬을 호출하여:
- prompt_plan.md 기반 작업 분해
- 팀 구성 및 Task 배정
- 실행 및 결과 집계
/handoff-verify 연동
팀 작업 완료 후 /handoff-verify로 통합 검증을 수행한다.
© sangrokjung, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/team-orchestrator of sangrokjung/claude-forge.
Open the folder on GitHubat commit 34d881d
Compare with similar skills
Team Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Team Orchestrator this skillsangrokjung/claude-forge | 852 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Paseo Advisor Second Opiniongetpaseo/paseo | 20k | 1 repos | ~756 | Automated safety check: Pass | Custom licence | |
| O2 Review Loopopenobserve/openobserve | 22k | — | ~3.7k | Automated safety check: Pass | AGPL-3.0 | |
| Harness Agent Team Designerrevfactory/harness | 9.1k | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| ClawTeam Multi-Agent Swarmwin4r/ClawTeam-OpenClaw | 1.5k | 1 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Sub-Agent Delegationcodewhale-hq/Codewhale | 41k | — | ~790 | Automated safety check: Pass | MIT |
Similar skills
O2 Review Loop
openobserve/openobserve
Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.
Harness Agent Team Designer
revfactory/harness
Designs a project-specific agent harness: defines specialist agents, writes the skills they follow, picks an execution mode and model for each, and keeps the setup maintained.
ClawTeam Multi-Agent Swarm
win4r/ClawTeam-OpenClaw
Launches a swarm of specialist Hermes agents in git-worktree-isolated tmux windows with a kanban board and file-based inboxes, using built-in templates like hedge-fund and code-review.
Sub-Agent Delegation
codewhale-hq/Codewhale
Guides when and how to split multi-step coding, research or verification work into focused sub-agent runs while the parent keeps integration and final checks.
Ruflo Multi-Agent Orchestration
ruvnet/ruflo
Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.
More from sangrokjung/claude-forge
All 24 skills in this repoDebugging Strategies
sangrokjung/claude-forge
Master systematic debugging techniques, profiling tools, and root cause analysis to efficiently track down bugs across any codebase or technology stack.
Dependency Upgrade
sangrokjung/claude-forge
Manage major dependency version upgrades with compatibility analysis, staged rollout, and comprehensive testing.
Skill Factory
sangrokjung/claude-forge
Analyze session work and automatically convert reusable patterns into Claude Code skills.
Cc Dev Agent
sangrokjung/claude-forge
A skill your agent uses when starting Claude Code projects, writing CLAUDE.md/spec.md, dispatching subagents, or requesting Agent Teams parallel development.
Continuous Learning V2
sangrokjung/claude-forge
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents.
Harness Diet
sangrokjung/claude-forge
Measure and shrink the always-loaded context of a Claude Code harness (CLAUDE.md + rules without paths frontmatter) back under budget — migrate narrative to reference files, convert rules to…
Related
Categories
Questions about Team Orchestrator
What does Team Orchestrator do?
A skill your agent uses when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation. Team Orchestrator is an agent skill from sangrokjung/claude-forge. Use when orchestrating Agent Teams for parallel development - team composition, task distribution, dependency management, and result aggregation.
When should I use Team Orchestrator?
Team Orchestrator fits situations like: orchestrating Agent Teams for parallel development - team composition; task distribution; dependency management; result aggregation.
How do I install Team Orchestrator in Claude Code?
Run `npx skills add sangrokjung/claude-forge --skill team-orchestrator -a claude-code`. Or copy the skill folder (skills/team-orchestrator in sangrokjung/claude-forge) into .claude/skills/team-orchestrator in your project. Claude Code loads it when a task matches its description.
How do I install Team Orchestrator in Codex?
Run `npx skills add sangrokjung/claude-forge --skill team-orchestrator -a codex`. Or copy the skill folder (skills/team-orchestrator in sangrokjung/claude-forge) into .agents/skills/team-orchestrator in your project. Codex loads it when a task matches its description.
Can I use Team Orchestrator in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sangrokjung/claude-forge --skill team-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-orchestrator, .gemini/skills/team-orchestrator, .github/skills/team-orchestrator and .opencode/skills/team-orchestrator in your project.
What does Team Orchestrator need to run?
SKILL.md names no scripts, command-line tools or credentials: Team Orchestrator is instructions for the agent only.
Does Team Orchestrator access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Team Orchestrator safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Team Orchestrator use?
Team Orchestrator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Team Orchestrator use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Team Orchestrator?
Skills that share tags, products or a category with Team Orchestrator: Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars), Harness Agent Team Designer (revfactory/harness, 9.1k stars) and ClawTeam Multi-Agent Swarm (win4r/ClawTeam-OpenClaw, 1.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Team Orchestrator?
sangrokjung (a GitHub user) maintains it in sangrokjung/claude-forge, which has 852 GitHub stars. The repository holds 24 skills in this directory. The repository was last updated on September 3, 2026.
Source: sangrokjung/claude-forge on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.