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 skills add cubha/claude-workflow-plugins --skill team-devgit clone --depth 1 https://github.com/cubha/claude-workflow-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/cubha/claude-workflow-plugins/team-dev)<a href="https://agentmods.dev/skills/cubha/claude-workflow-plugins/team-dev"><img src="https://agentmods.dev/badge/skills/cubha/claude-workflow-plugins/team-dev/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cubha/claude-workflow-plugins/team-dev"><img src="https://agentmods.dev/badge/skills/cubha/claude-workflow-plugins/team-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00078 | $0.02069 |
| Opus 5.5 | $0.00031 | $0.00828 |
| Sonnet 5.5 | $0.00016 | $0.00414 |
| Haiku 4.5 | $0.00008 | $0.00207 |
Grade A, and why
team-dev 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 1mo 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Team Dev — 팀 에이전트 병렬 개발 오케스트레이터
$ARGUMENTS 에 대해 SubTask를 의존성 분석하고, 병렬 가능 그룹으로 분류한 후, 팀원 에이전트가 worktree 격리 환경에서 동시 구현한다.
ANALYZE → [ DISPATCH → BUILD → VERIFY → INTEGRATE ] × 그룹 → COMPLETE
전제 조건
- Git 저장소 필수 — worktree 격리를 위해
git init이 완료된 상태여야 한다 - SubTask 목록 필수 — SubTask 목록을 입력으로 받는다 ($ARGUMENTS에 있거나, 자연어 기능 설명에서 분리 가능해야 한다). 없으면 AskUserQuestion으로 요청한다
- 프로젝트 규칙 문서(선택) — CLAUDE.md 등 프로젝트 규칙 파일이 있으면 팀원 프롬프트의 컨텍스트로 주입한다
- 검증 스크립트(선택) —
verify.sh·npm test·npm run build등 프로젝트 검증 수단이 있으면 각 SubTask 완료 후 및 통합 시 실행한다 (없으면 정적 검증 단계를 생략한다)
Phase 0: PARSE — 인자 파싱
$ARGUMENTS에서 아래를 추출한다:
| 항목 | 추출 대상 | 기본값 |
|---|---|---|
| SubTask 목록 | TaskList 도구의 기존 목록 또는 자연어 기능 설명 | (필수 — 없으면 AskUserQuestion) |
| --auto | 그룹 간 자동 진행 여부 | OFF (그룹 완료마다 확인) |
| --dry-run | 의존성 분석 + 그룹 분류만 수행 | OFF |
| --tdd | TDD RED 게이트 발동 (test-first 구현) | OFF |
| --no-tdd | TDD 제안·태그 모두 끔 (escape hatch) | OFF |
TDD 의미론: 인터랙티브(
--auto없음)에서는 적격 SubTask에[TDD]를 붙여 Phase 1-6 승인게이트에 제안 노출한다.--auto단독이면 자동태그 OFF(전부 test-after),--auto --tdd면 적격 SubTask에 자동 부착(제안 생략),--no-tdd면 판단·제안 모두 끈다. 적격 기준과 절대제외는 아래 Phase 1-1-1 참조. team-dev는 git 필수라 RED 게이트의 실패테스트 선커밋 안전망이 항상 가용하다.
실행 모드 분기
| 모드 | 플래그 | 실행 방식 |
|---|---|---|
| 서브에이전트 모드 (기본) | 없음 | Agent 도구로 worktree 격리 병렬 spawn |
| 에이전트 팀 모드 (experimental) | (Agent Teams 활성 시) | 팀 리더가 팀원 인스턴스 생성, Task 할당, 코드 리뷰, 통합 검증 |
에이전트 팀 모드는 Claude Code의 experimental Agent Teams 기능이 활성화된 환경에서만 동작한다. 활성화돼 있지 않으면 기본 서브에이전트 모드로 진행한다. 상세는 phase-dispatch.md [B] 참조.
Phase 1: ANALYZE — 의존성 분석 및 그룹 분류
SubTask 수집 → 컨텍스트 수집 → UI/UX 설계 → 의존성 분석 → 그룹 구성 → 사용자 승인. 상세 절차는 phase-analyze.md 참조.
Phase 2: DISPATCH — 팀원 배포
그룹 내 각 SubTask를 팀원 에이전트에게 배포한다. 서브에이전트 모드(기본)와 에이전트 팀 모드(experimental) 두 가지 분기. 상세 절차 및 프롬프트 템플릿은 phase-dispatch.md 참조.
Phase 3: BUILD — 빌드 대기
run_in_background: true로 실행했으므로, 각 에이전트 완료 시 자동 알림을 받는다.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 180 lines · 78 tokens per session scan A 01bbcbcde21c
team-dev is a skill published in the GitHub repository cubha/claude-workflow-plugins (2 stars, last pushed 3mo ago), licensed MIT. It adds 78 tokens to every session and 2,069 once invoked, about $0.0003 per session on Opus 5.5. 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
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.
orchestrate-issues
Drive a whole graph of GitHub issues to completion using background subagents. Queries the unblocked frontier through native GitHub issue dependencies, dispatches one implementer per ready issue into an isolated worktree, runs a spec-review agent against the result, lands the PR, then re-queries as each merge opens…
github-issue-triage
A GitHub issue organiser for open problems and requests in a software project. GitHub is a service where teams store code and track issues.
start-task
Bootstrap a task into a synced feature branch — one shot, zero confirmations. Detects the source from the args: GitHub issue ('#100', 'issue 100', 'gh issue 100', or bare '100'), Jira key ('PROJ-42'), or a local spec file path; ad-hoc conversation otherwise. Fetches the task, derives {type}/{number}/{slug}, syncs the…
sync
Brings the canonical page current after a release by auditing which finished changes on working pages never made it there, applying them and archiving the working copies, each step behind its own preview and go. Triggers - "/fig:sync", "find what never made it into canonical", "bring the canonical page current", "정본…
parallel-execution-strategy
Use when 3+ independent tasks are ready in .forge/tasks.yaml and multiple agents will work concurrently, when assessing file-conflict risk before dispatching parallel work, when planning branch and merge sequencing for a sprint, or when prior parallel runs have caused merge nightmares.