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.
curl -O https://raw.githubusercontent.com/gosha70/code-copilot-team/master/adapters/github-copilot/.github/instructions/review-loop.instructions.mdgit 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/instructions/gosha70/code-copilot-team/review-loop)<a href="https://agentmods.dev/instructions/gosha70/code-copilot-team/review-loop"><img src="https://agentmods.dev/badge/instructions/gosha70/code-copilot-team/review-loop.svg" alt="Measured on agentmods" 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.01551 | $0.01551 |
| Opus 5 | $0.00776 | $0.00776 |
| Sonnet 5 | $0.00310 | $0.00310 |
| Haiku 4.5 | $0.00155 | $0.00155 |
Grade A, and why
code-copilot-team review-loop.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.
How it starts
The opening of the file, as written. The whole thing — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Loop Protocol
Agent-driven peer review loop for Build and Plan phases. The Build agent drives the loop; the reviewer is a separate, read-only LLM.
Loop Architecture
The review loop is agent-driven: the Build agent calls /review-submit, which invokes review-round-runner.sh as a synchronous subprocess. The runner executes one round and returns. The agent reads the result and decides the next action. There is no long-running orchestrator.
Driver-as-submitter mode: under the auto-build loop (auto-build-loop.md), scripts/auto-build-loop.sh plays the /review-submit role — it initializes .cct/review/state.json, invokes the runner with CCT_REVIEW_BASE_REF=<phase-base> so the whole multi-commit phase diff is reviewed (the default remains HEAD~1), commits review fixes itself, and injects commit_ref into fixed dispositions. The runner's contract (exit codes, file formats, breakers, sandbox) is unchanged.
Agent completes work → /review-submit → review-round-runner.sh (one round)
↓
EXIT 0 (PASS) → loop-summary.json → /phase-complete
EXIT 1 (FAIL) → findings-round-N.json → agent fixes → /review-submit
EXIT 2 (BREAKER) → breaker-tripped.json → agent stops → /review-decide
File Contract
All review-loop artifacts live under .cct/review/ during the active loop.
| File | Written By | Purpose |
|---|---|---|
state.json |
/review-submit (init), runner (update) |
Loop state: round, attempt, findings, breaker counters |
findings-round-N.json |
Runner | Structured findings for round N |
resolution-round-N.json |
Build agent | Builder's response to each finding |
breaker-tripped.json |
Runner | Breaker context, awaiting /review-decide |
decision.json |
/review-decide |
Human's decision: approve, reject, or retry |
loop-summary.json |
Runner (PASS) or agent (bypass) | Final record of all rounds |
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 · 136 lines · 1,551 tokens per session scan A 2e888f684d4e
code-copilot-team review-loop.instructions.md is an instructions file published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed today), licensed MIT. It adds 1,551 tokens to every session, about $0.0078 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 instructions, from other repositories
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.
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.