multi-review

multi-review is a skill for Claude Code from phobologic/claude_code_helpers. It costs 49 tokens per session (2,461 once invoked), scanned A, original, MIT.

A coordinated code review that uses several specialist agents to examine logical correctness, performance, readability, and security in parallel.

In plain words
What is it for?
Use it for uncommitted changes, a commit range, or selected files. It creates tk tickets when available or writes a report when tk is not installed.
Why use it?
Reviewing the same changes from different technical angles can reveal problems a single review may miss, then combine duplicate findings into one result.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: model in frontmatter; mentions subagents.

Good fit Use it for uncommitted changes, a commit range, or selected files. It creates tk tickets when available or writes a report when tk is not installed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/phobologic/claude_code_helpers/multi-review
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 phobologic/claude_code_helpers --skill multi-review
Clone the repo
git clone --depth 1 https://github.com/phobologic/claude_code_helpers

Made for: Claude Code.

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 multi-review

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/phobologic/claude_code_helpers/multi-review"><img src="https://agentmods.dev/badge/skills/phobologic/claude_code_helpers/multi-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,461 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.00049 $0.02461
Opus 5.5 $0.00020 $0.00984
Sonnet 5.5 $0.00010 $0.00492
Haiku 4.5 $0.00005 $0.00246

Measured 5d ago against content hash a327468a0d64, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

multi-review 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 5d 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.

skills/multi-review/SKILL.md · 234 lines

How it starts

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

Multiple Code Reviewers

You are the team lead for a parallel code review. Your job is to orchestrate four specialized reviewer agents, receive their findings, deduplicate, and create tickets (or write a report). You never review code yourself — that's the reviewers' job.

Step 1: Setup and collect context

Parse $ARGUMENTS to determine scope, then run the setup script in a single Bash call:

  • No arguments (default — uncommitted changes): review-setup
  • Commit references (e.g., "last 3 commits", "since abc123", "HEAD~5"): Determine the appropriate base ref from the user's intent, then review-setup --scope commit-range --base-ref <ref>
  • Specific files (e.g., "Review src/auth.py src/models.py"): review-setup --scope files --files src/auth.py src/models.py

Capture TK_AVAILABLE, REVIEW_CMD, and FILES_COUNT from the output.

If FILES_COUNT is 0, tell the user there are no files to review and stop.

Step 2: Create the epic (if TK_AVAILABLE)

If TK_AVAILABLE is true:

  1. Examine the changed files list and generate a short, descriptive title summarizing what's being reviewed (e.g., "Review: Auth module refactor" or "Review: API endpoint updates and test fixes").
  2. Create an epic with a timestamp for uniqueness:
EPIC_ID=$(tk create "<generated title> (<YYYY-MM-DD HH:MM>)" -t epic -p 2 --tags code-review -d "<brief summary of changes being reviewed>")
  1. Note the EPIC_ID — you'll use it to create tickets during the coordination loop.

Step 3: Spawn reviewers

Spawn all four reviewers in parallel as background agents. Each agent receives TEAM_MODE=true and REVIEW_CMD=<review_cmd> in its prompt.

Agent({
  prompt: "TEAM_MODE=true REVIEW_CMD=<review_cmd> -- Review ONLY files in .code-review/changed-files.txt",
  subagent_type: "code-reviewer-1",
  model: "sonnet",
  name: "reviewer-logic"
})

Agent({
  prompt: "TEAM_MODE=true REVIEW_CMD=<review_cmd> -- Review ONLY files in .code-review/changed-files.txt",
  subagent_type: "code-reviewer-2",
  model: "sonnet",
  name: "reviewer-perf"
})

Agent({
  prompt: "TEAM_MODE=true REVIEW_CMD=<review_cmd> -- Review ONLY files in .code-review/changed-files.txt",
  subagent_type: "code-reviewer-3",
  model: "sonnet",
  name: "reviewer-structure"
})

Agent({
  prompt: "TEAM_MODE=true REVIEW_CMD=<review_cmd> -- Review ONLY files in .code-review/changed-files.txt",
  subagent_type: "security-reviewer",
  model: "sonnet",
  name: "reviewer-security"
})

Read the full file on GitHub · 234 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. 5d ago Changed · +6 lines a327468a0d64
  2. 12d ago Changed · +3 lines c60b8bbf0cc3
  3. 1mo ago First seen · 225 lines · 49 tokens per session scan A 9043289dfb23

Subscribe to this mod's changes

multi-review is a skill published in the GitHub repository phobologic/claude_code_helpers (5 stars, last pushed 5d ago), licensed MIT. It adds 49 tokens to every session and 2,461 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

autoreview

Structured code review through the shared OpenClaw agent-skills installation.

openclaw/clawhub · 17 tokens

omh-code-review

This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).

rlaope/oh-my-hermes · 48 tokens

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"…

umputun/revdiff · 84 tokens

asplos-writing-style

Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…

brycewang-stanford/Awesome-Journal-Skills · 65 tokens

explore-unknowns

Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…

dzhng/skills · 162 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens