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.
git clone --depth 1 https://github.com/gosha70/code-copilot-teamWrote 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/rules/gosha70/code-copilot-team/agent-team-protocol)<a href="https://agentmods.dev/rules/gosha70/code-copilot-team/agent-team-protocol"><img src="https://agentmods.dev/badge/rules/gosha70/code-copilot-team/agent-team-protocol/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/rules/gosha70/code-copilot-team/agent-team-protocol"><img src="https://agentmods.dev/badge/rules/gosha70/code-copilot-team/agent-team-protocol.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.00026 | $0.02943 |
| Opus 5.5 | $0.00010 | $0.01177 |
| Sonnet 5.5 | $0.00005 | $0.00589 |
| Haiku 4.5 | $0.00003 | $0.00294 |
Grade A, and why
agent-team-protocol 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 — 195 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.mdfor 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.mdwithspec_modefrontmatter. - For
fullorlightweight: Plan also writesspec.md. User approves both before Build. - For
none: User approvesplan.mdonly. Build proceeds without a spec gate. - All
[NEEDS CLARIFICATION]markers inspec.mdmust 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-submitonce (advisory). A FAIL is logged asplan-consult.mdbut does not block Build entry. Proceed to/phase-completeregardless of verdict. - Build agent: run
/review-submitto start the agent-driven review loop. On FAIL, address findings and resubmit. On PASS, proceed to/phase-complete. Thebuild-review.mdartifact must exist withverdict: PASSor approved bypass before the session can end.
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 · 195 lines · 26 tokens per session scan A e576271f9107
agent-team-protocol is a cursor rule published in the GitHub repository gosha70/code-copilot-team (7 stars, last pushed 17d ago), licensed MIT. It adds 26 tokens to every session and 2,943 once invoked, about $0.0001 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 cursor rules, from other repositories
cairn-commit-network
Commits that run cairn hooks need unsandboxed network.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).