agent-collaboration

agent-collaboration is a skill for Claude Code, Codex from alonf/MCPPythonDemo. It costs 22 tokens per session (443 once invoked), scanned A, a copy of agent-collaboration, MIT.

Shared instructions for agents working as a team, covering worktree awareness, recording decisions, asking for help, and reviewing changes.

In plain words
What is it for?
Finding the correct team repository, documenting decisions, communicating across agents, and following the team's review process.
Why use it?
It keeps multiple agents coordinated and prevents decisions or file locations from being lost.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Finding the correct team repository, documenting decisions, communicating across agents, and following the team's review process.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alonf/mcppythondemo/agent-collaboration
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.

Any agent
npx skills add alonf/MCPPythonDemo --skill agent-collaboration
Clone the repo
git clone --depth 1 https://github.com/alonf/MCPPythonDemo

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 agent-collaboration

README.md
[![agentmods](https://agentmods.dev/badge/skills/alonf/mcppythondemo/agent-collaboration/github.svg)](https://agentmods.dev/skills/alonf/mcppythondemo/agent-collaboration)
Your own site
<a href="https://agentmods.dev/skills/alonf/mcppythondemo/agent-collaboration"><img src="https://agentmods.dev/badge/skills/alonf/mcppythondemo/agent-collaboration/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.

agentmods 80×15 button for agent-collaboration

Your own site · 80×15
<a href="https://agentmods.dev/skills/alonf/mcppythondemo/agent-collaboration"><img src="https://agentmods.dev/badge/skills/alonf/mcppythondemo/agent-collaboration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 443 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.1 $0.00022 $0.00443
Opus 5.5 $0.00009 $0.00177
Sonnet 5.5 $0.00004 $0.00089
Haiku 4.5 $0.00002 $0.00044

Measured 1mo ago against content hash 8a723a95dfb5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

Origin

This is a copy

100% identical to agent-collaboration — 84 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.squad/templates/skills/agent-collaboration/SKILL.md · 43 lines

What it actually says

Context

Every agent on the team follows identical collaboration patterns for worktree awareness, decision recording, and cross-agent communication. These were previously duplicated in every charter's Collaboration section (~300 bytes × 18 agents = ~5.4KB of redundant context). Now centralized here.

The coordinator's spawn prompt already instructs agents to read decisions.md and their history.md. This skill adds the patterns for WRITING decisions and requesting help.

Patterns

Worktree Awareness

Use the TEAM ROOT path provided in your spawn prompt. All .squad/ paths are relative to this root. If TEAM ROOT is not provided (rare), run git rev-parse --show-toplevel as fallback. Never assume CWD is the repo root.

Decision Recording

After making a decision that affects other team members, write it to: .squad/decisions/inbox/{your-name}-{brief-slug}.md

Format:

### {date}: {decision title}
**By:** {Your Name}
**What:** {the decision}
**Why:** {rationale}

Cross-Agent Communication

If you need another team member's input, say so in your response. The coordinator will bring them in. Don't try to do work outside your domain.

Reviewer Protocol

If you have reviewer authority and reject work: the original author is locked out from revising that artifact. A different agent must own the revision. State who should revise in your rejection response.

Anti-Patterns

  • Don't read all agent charters — you only need your own context + decisions.md
  • Don't write directly to .squad/decisions.md — always use the inbox drop-box
  • Don't modify other agents' history.md files — that's Scribe's job
  • Don't assume CWD is the repo root — always use TEAM ROOT
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. 1mo ago First seen · 43 lines · 22 tokens per session scan A 8a723a95dfb5

Subscribe to this mod's changes

agent-collaboration is a skill published in the GitHub repository alonf/MCPPythonDemo (0 stars, last pushed 6mo ago), licensed MIT. It adds 22 tokens to every session and 443 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-collaboration, differing in 84 lines, and is treated as a copy.

Related

Other skills, from other repositories

story-readiness

Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.

Donchitos/Claude-Code-Game-Studios · 35 tokens

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens