collaborate

A collaboration command for multiple people or coding agents working on the same project from different machines. It shares ideas, assigns tasks, coordinates decisions, and combines completed work.

In plain words
What is it for?
Use it for group brainstorming, task assignment, asynchronous decisions, and coordinating work through either a realtime service or a Git-based polling mode.
Why use it?
Distributed teams need a shared way to claim work and exchange updates without waiting for every decision to be made synchronously.

Command

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 commands/lucasduys/forge/collaborate
Clone the repo
git clone --depth 1 https://github.com/LucasDuys/forge
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,531 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.00018 $0.01531
Opus 5 $0.00009 $0.00766
Sonnet 5 $0.00004 $0.00306
Haiku 4.5 $0.00002 $0.00153

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

Security

Grade A, and why

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

commands/collaborate.md · 111 lines

How it starts

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

Forge Collaborate

Activates hackathon-native multiplayer mode: N users on different machines brain-dump ideas, AI consolidates into categorized tasks, tasks dispatch across machines via a distributed claim queue, each agent squash-merges its own completed task. Forward-motion during execute: AI picks + flags decisions, humans override async.

Prerequisites

Two transport modes are supported. Pick one BEFORE running /forge:collaborate start:

  • Realtime (Ably) — sub-second cross-machine latency via WebSockets. Requires:
    1. The ably npm package installed: npm install ably in your project (or globally). It's declared an OPTIONAL peerDependency in the plugin's package.json, so /forge:collaborate start hard-fails with "forge:collab realtime mode requires the ably peer dependency" until you install it.
    2. An Ably API key in your environment: export ABLY_KEY="<your-key>". Free tier at https://ably.com/sign-up covers typical hackathon teams (6M messages/month, 200 peak connections).
  • Polling (zero-setup) — coordination via a dedicated forge/collab-state git branch, ~2.5s latency. No extra dependencies, no API keys. Pass --polling to /forge:collaborate start to opt into this path even when ABLY_KEY is in env.

If neither is configured and --polling is not passed, start prints a setup guide and exits.

Subcommands

Command What it does
/forge:collaborate start Initialize collab state, print session code derived from repo's origin URL
/forge:collaborate join Sync with existing session in this repo (git pull + subscribe)
/forge:collaborate brainstorm Enter chat-mode brain-dump; agent iterates with you and writes .forge/collab/brainstorm/inputs-<handle>.md on accept
/forge:collaborate status Show participants online, active claims, open flags
/forge:collaborate claim <taskId> Explicitly reserve a specific task
/forge:collaborate flags List all forward-motion flags with status
/forge:collaborate override <flagId> <new-decision> Override an AI decision, mark flag overridden
/forge:collaborate leave Release claims and disconnect
/forge:collaborate recover Diagnose and repair a stale collab session (crash between start/leave steps)

Read the full file on GitHub · 111 lines

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. 2d ago First seen · 111 lines · 18 tokens per session scan A e169f1f1844e

Subscribe to this mod's changes

collaborate is a command published in the GitHub repository LucasDuys/forge (55 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 1,531 once invoked, about $0.0001 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-30.