collaboration-workflow

collaboration-workflow is a skill for Claude Code, Codex from opensquad-ai/opensquad. It costs 89 tokens per session (4,400 once invoked), scanned A, original, MIT.

A four-phase workflow for coordinating several agents with explicit user approval between requirements, solution discussion, execution, and acceptance. It includes a shared board and role-specific reporting conventions.

In plain words
What is it for?
Use it to start collaboration sessions, coordinate agents, manage the collaboration board, assign tasks, and combine research or analysis into a deliverable.
Why use it?
It prevents a team from moving to the next phase without the operator confirming the previous one. It also gives collaborators a common way to assign work and report progress.

Skill for Claude CodeCodex

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 skills/opensquad-ai/opensquad/collaboration-workflow
Any agent
npx skills add opensquad-ai/opensquad --skill collaboration-workflow
Clone the repo
git clone --depth 1 https://github.com/opensquad-ai/opensquad

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for collaboration-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/opensquad-ai/opensquad/collaboration-workflow.svg)](https://agentmods.dev/skills/opensquad-ai/opensquad/collaboration-workflow)
Your own site
<a href="https://agentmods.dev/skills/opensquad-ai/opensquad/collaboration-workflow"><img src="https://agentmods.dev/badge/skills/opensquad-ai/opensquad/collaboration-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,400 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.00089 $0.04400
Opus 5 $0.00044 $0.02200
Sonnet 5 $0.00018 $0.00880
Haiku 4.5 $0.00009 $0.00440

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

Security

Grade A, and why

collaboration-workflow 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.

src/skills/collaboration-workflow/SKILL.md · 453 lines

How it starts

The opening of the file, as written. The whole thing — 453 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Collaboration Workflow Skill

Overview

This skill provides a complete guide to the OpenSquad multi-agent collaboration system. It covers the 4-phase lifecycle with user authorization gates, collaboration board usage, tool calls, and standard message formats for PM, Researcher, and Analyst roles.

Core Rule: User Authorization Required at Every Phase

Each phase must be explicitly approved by the user before proceeding to the next. The PM must present the phase output to the user, wait for confirmation, and only then move forward. Never skip authorization or proceed without user approval.

Phase 1: 确定需求 ──→ 向用户展示需求 ──→ 用户确认 ──→ 进入 Phase 2
Phase 2: 讨论方案 ──→ 向用户展示方案 ──→ 用户确认 ──→ 进入 Phase 3
Phase 3: 开始执行 ──→ 向用户展示进度 ──→ 用户确认 ──→ 进入 Phase 4
Phase 4: 完成验收 ──→ 向用户交付成果 ──→ 用户确认 ──→ 协作结束

When to Use This Skill

Load this skill when:

  • Starting a new collaboration session
  • Coordinating multiple agents on a shared task
  • Writing or reading the collaboration board
  • Assigning tasks to team members
  • Reporting progress or findings
  • Synthesizing research results into a report

Core Concepts

Collaboration Board — 4 Areas

The collaboration board is the central coordination surface. It has four distinct areas:

Area Purpose Who writes item_type
需求区 (Requirements) Research scope, quality expectations PM requirement
方案区 (Plan) Final report document, task checklist overview PM + Analyst plan + task
任务分配区 (Tasks) Editable task list with inline editing PM (create), any agent (edit) task
任务进度区 (Progress) Auto-synced per-agent progress, latest tool calls Auto (runner) status

The item_key — Multiple Entries Per Type

Every board entry is uniquely identified by (collab_id, agent_id, item_type, item_key). The item_key allows multiple independent entries of the same type:

PM creates:
  board_update(item_type="requirement", item_key="req_scope")       → 需求1
  board_update(item_type="task", item_key="research_diagnostic")    → 任务1
  board_update(item_type="task", item_key="research_treatment")     → 任务2

Researcher updates:
  board_update(item_type="task", item_key="research_diagnostic", progress=50)
  board_update(item_type="task", item_key="research_diagnostic", done, 100%)

PM writes report:
  board_update(item_type="plan", item_key="final_report", content="...")

Read the full file on GitHub · 453 lines

Files

What ships with it

1 file 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.

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 · 453 lines · 89 tokens per session scan A a9eb1cae73b0

Subscribe to this mod's changes

collaboration-workflow is a skill published in the GitHub repository opensquad-ai/opensquad (5 stars, last pushed 20d ago), licensed MIT. It adds 89 tokens to every session and 4,400 once invoked, about $0.0004 per session on Opus 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.