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 agentmods add rules/gosha70/code-copilot-team/review-loopgit clone --depth 1 https://github.com/gosha70/code-copilot-teamWhat 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 | $0.00026 | $0.01580 |
| Opus 5 | $0.00013 | $0.00790 |
| Sonnet 5 | $0.00005 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
Grade A, and why
review-loop 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 yesterday.
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 — 137 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.
- yesterday First seen · 137 lines · 26 tokens per session scan A 8f116e7fca95
review-loop is a cursor rule published in the GitHub repository gosha70/code-copilot-team (6 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,580 once invoked, about $0.0001 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-08-31.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.