It is for organizing multi-agent software tasks, requiring a plan before implementation, asking project questions early, and defining test and review expectations.

It gives team-based coding work clear handoffs and approval points, reducing confusion about who plans, builds, reviews, or makes decisions.

How gosha70/code-copilot-team configures GitHub Copilot

Q: What is code-copilot-team agent-team-protocol.instructions.md?

A set of rules for coordinating multiple coding assistants through planning, approval, building, and review phases. It explains when one assistant works alone and when assistants may collaborate.

Reuse

Borrowing it

Nothing to install: this file belongs to gosha70/code-copilot-team. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/agent-team-protocol.instructions.md

Clone the repo

git clone --depth 1 https://github.com/gosha70/code-copilot-team

Made for: GitHub Copilot.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/agent-team-protocol.svg)](https://agentmods.dev/instructions/gosha70/code-copilot-team/agent-team-protocol)

Your own site

<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/agent-team-protocol"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/agent-team-protocol.svg" alt="Measured on agentmods" height="20"></a>

Per session 2,914 This file is loaded in full into every session.

When invoked 2,914 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.02914	$0.02914
Opus 5	$0.01457	$0.01457
Sonnet 5	$0.00583	$0.00583
Haiku 4.5	$0.00291	$0.00291

Measured 3d ago against content hash 04c8eb36440b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

code-copilot-team agent-team-protocol.instructions.md 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.

adapters/github-copilot/.github/instructions/agent-team-protocol.instructions.md · 194 lines

How it starts

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

Agent Team Protocol

Note on naming. This document uses "team" to mean a group of subagents working within a single session, coordinated by a Team Lead via the copilot's delegation tool. Some tools also offer experimental multi-session coordination features (see § "Multi-Session Coordination" at the bottom of this document). The two are different things.

Rules governing multi-agent delegation, phased workflows, and model selection.

Three-Phase Workflow

Every non-trivial task follows three phases with distinct behaviors:

Phase 1 — PLAN (Single Agent)

Model: Highest-capability (e.g., Opus) · Effort: xhigh (Opus 4.7) / high (other models)
Work alone. Do NOT delegate to sub-agents.
Read the full codebase context, understand architecture, identify risks.
Ask clarifying questions about data model shape, auth strategy, UI layout, and output formats BEFORE producing the plan. (See clarification-protocol.md for the full protocol and data model review gate.)
Produce a concrete plan: files to touch, interfaces to change, test strategy.
Get user approval before moving to Phase 2.

Plan Approval Gate

Between Phase 1 (Plan) and Phase 2 (Build), a spec gate applies:

Plan always writes specs/<feature-id>/plan.md with spec_mode frontmatter.
For full or lightweight: Plan also writes spec.md. User approves both before Build.
For none: User approves plan.md only. Build proceeds without a spec gate.
All [NEEDS CLARIFICATION] markers in spec.md must be resolved before Build starts.

See spec-workflow.md for risk classification and required sections.

Collaboration Gate (Dual Mode)

When collaboration_mode: dual in plan.md frontmatter OR the environment variable CCT_PEER_REVIEW_ENABLED is true:

Plan agent: run /review-submit once (advisory). A FAIL is logged as plan-consult.md but does not block Build entry. Proceed to /phase-complete regardless of verdict.
Build agent: run /review-submit to start the agent-driven review loop. On FAIL, address findings and resubmit. On PASS, proceed to /phase-complete. The build-review.md artifact must exist with verdict: PASS or approved bypass before the session can end.

Read the full file on GitHub · 194 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.

3d ago First seen · 194 lines · 2,914 tokens per session scan A 04c8eb36440b

Subscribe to this mod's changes

code-copilot-team agent-team-protocol.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 2,914 tokens to every session, about $0.0146 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-09-03.

Building agents Planning

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

code-copilot-team: Instructions file for GitHub Copilot