review-arena

review-arena is a skill for Claude Code from romiluz13/cc-teams. It costs 26 tokens per session (2,996 once invoked), scanned A, original, MIT.

A structured code-review process that asks several specialized reviewers to inspect the same changes independently and then challenge one another’s findings.

In plain words
What is it for?
Use it to check code for issues such as injection risks, slow queries, memory leaks, difficult-to-maintain patterns, inaccessible interfaces, or breaking API changes.
Why use it?
It reduces the chance that one reviewer misses a security, performance, quality, accessibility, or API-compatibility problem. The reviewers only report findings; they do not change files.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the cc-teams plugin — 17 skills, 14 agents shipped together

Good fit Use it to check code for issues such as injection risks, slow queries, memory leaks, difficult-to-maintain patterns, inaccessible interfaces, or breaking API changes.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/romiluz13/cc-teams/review-arena
Install

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.

Any agent
npx skills add romiluz13/cc-teams --skill review-arena
Clone the repo
git clone --depth 1 https://github.com/romiluz13/cc-teams

Made for: Claude Code.

Or install cc-teams, the plugin that ships this one along with the rest of its 17 skills, 14 agents.

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.

agentmods badge for review-arena

README.md
[![agentmods](https://agentmods.dev/badge/skills/romiluz13/cc-teams/review-arena/github.svg)](https://agentmods.dev/skills/romiluz13/cc-teams/review-arena)
Your own site
<a href="https://agentmods.dev/skills/romiluz13/cc-teams/review-arena"><img src="https://agentmods.dev/badge/skills/romiluz13/cc-teams/review-arena/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.

agentmods 80×15 button for review-arena

Your own site · 80×15
<a href="https://agentmods.dev/skills/romiluz13/cc-teams/review-arena"><img src="https://agentmods.dev/badge/skills/romiluz13/cc-teams/review-arena.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 26 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,996 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00026 $0.02996
Opus 5 $0.00013 $0.01498
Sonnet 5 $0.00005 $0.00599
Haiku 4.5 $0.00003 $0.00300

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

Security

Grade A, and why

review-arena 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 9d 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.

plugins/cc-teams/skills/review-arena/SKILL.md · 343 lines

How it starts

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

Review Arena Protocol

Overview

Review Arena uses 3 specialized reviewer teammates who first review independently, then challenge each other's findings via peer messaging, producing a unified verdict that's stronger than any single review.

Core principle: First verify it works, THEN verify it's good.


Team Composition

Teammate Role Focus Areas Mode When Active
security-reviewer Security specialist Auth, injection, secrets, OWASP top 10, XSS, CSRF READ-ONLY Always
performance-reviewer Performance specialist N+1 queries, memory leaks, bundle size, caching, loops READ-ONLY Always
quality-reviewer Quality specialist Patterns, naming, complexity, error handling, tests, duplication READ-ONLY Always
accessibility-reviewer A11y specialist (conditional) WCAG 2.1 AA, keyboard nav, ARIA, semantic HTML, contrast READ-ONLY When UI files detected
api-contract-reviewer Contract validator (conditional) Breaking changes, route/schema diffs, type compatibility READ-ONLY When API files detected

All reviewers are READ-ONLY. They cannot edit files. They output Router Contracts with Memory Notes.

Conditional spawning: Lead checks builder's FILES_MODIFIED field after hunter completes:

  • Contains .tsx|.jsx|.html|.css|.vue → spawn accessibility-reviewer
  • Contains routes/|api/|endpoints/|handlers/|controllers/ → spawn api-contract-reviewer

Two-Stage Review Process (Each Reviewer)

Stage 1: Spec Compliance Review

Does it do what was asked?

  1. Read the Requirements — What was requested? Acceptance criteria? Edge cases?
  2. Trace the Implementation — Does the code implement each requirement? All edge cases handled?
  3. Test Functionality — Run the tests. Manual test if needed. Verify outputs.

Gate: Only proceed to Stage 2 if Stage 1 passes.

Stage 2: Code Quality Review (Per Specialty)

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

  1. 9d ago First seen · 343 lines · 26 tokens per session scan A c3ba6032d008

Subscribe to this mod's changes

review-arena is a skill published in the GitHub repository romiluz13/cc-teams (5 stars, last pushed 5mo ago), licensed MIT. It adds 26 tokens to every session and 2,996 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens