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.
npx skills add gosha70/code-copilot-team --skill agent-team-protocolgit 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/skills/gosha70/code-copilot-team/agent-team-protocol)<a href="https://agentmods.dev/skills/gosha70/code-copilot-team/agent-team-protocol"><img src="https://agentmods.dev/badge/skills/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/skills/gosha70/code-copilot-team/agent-team-protocol"><img src="https://agentmods.dev/badge/skills/gosha70/code-copilot-team/agent-team-protocol.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.02944 |
| Opus 5 | $0.00015 | $0.01472 |
| Sonnet 5 | $0.00006 | $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 7d 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 — 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.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.
- 7d ago First seen · 194 lines · 31 tokens per session scan A 2f7a3bd86a69
agent-team-protocol is a skill published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 2,944 once invoked, about $0.0002 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.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…