A multi-phase codebase review that first maps components and their connections, then runs specialized reviewers in parallel. It records each worker's result and treats missing results as failures.

Use it for deep reviews of a whole codebase or large change, including API contracts, security, data integrity, cleanup, timing, and user-interface race issues.

It looks for cross-component logic and flow problems that a review of individual files may miss, while ensuring incomplete reviews are visible.

team-review — Command for Claude Code by acaprino/daodan

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.

Clone the repo

git clone --depth 1 https://github.com/acaprino/daodan

Made for: Claude Code.

Or install senior-review, the plugin that ships this one along with the rest of its 3 skills, 3 commands, 12 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/acaprino/daodan/team-review/github.svg)](https://agentmods.dev/commands/acaprino/daodan/team-review)

Your own site

<a href="https://agentmods.dev/commands/acaprino/daodan/team-review"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/team-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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/acaprino/daodan/team-review"><img src="https://agentmods.dev/badge/commands/acaprino/daodan/team-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,004 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.02004
Opus 5.5	$0.00000	$0.00802
Sonnet 5.5	$0.00000	$0.00401
Haiku 4.5	$0.00000	$0.00200

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

Security

Grade A, and why

team-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 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.

exports/claude/plugins/senior-review/commands/team-review.md · 92 lines

How it starts

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

team-review

Execution harness

Selected topology: native-team. Use native Agent Teams when they are enabled in this session; otherwise dispatch the same roles as isolated subagents. Both paths satisfy the same contract, and which one answered changes nothing a reader of the report can observe. Declared worker isolation: required.

Harness obligations, none of them optional:

Every dispatched worker runs in its own context and reads only coordinator-declared inputs. Independent reviewers never read peer results before their own delivery; no worker runs in the coordinator's context.
Follow the dispatch plan below in phase order. A phase starts only after every phase it needs has closed, and a phase closes only when every worker it dispatched is recorded delivered or failed. A missing result is a recorded failure, never a silently shorter report.
Dispatch only roles from this set, as the phase graph or loaded method requires: abstraction-architect:abstraction-architect-agent, api-contract-auditor, chicken-egg-detector, cleanup-auditor, code-auditor, codebase-xray:semantic-interconnect-mapper, data-integrity-auditor, distributed-flow-auditor, logic-integrity-auditor, platform-engineering:platform-reviewer, premise-auditor, project-protocol:isolated-worker, react-development:react-performance-optimizer, repo-hygiene:workspace-auditor, resource-lifecycle-auditor, security-auditor, temporal-resilience-auditor, testing:test-suite-auditor, typescript-development:type-safety-auditor, ui-race-auditor
Workers may write only intermediate reports explicitly assigned by the coordinator. The final report artifact has one exclusive owner in its declaring phase.

Dispatch plan:

scope: runs in the orchestrating context; produces artifact:review-brief.
context-building: runs in the orchestrating context; needs scope; consumes artifact:review-brief; produces artifact:context-map.
dimension-detection: runs in the orchestrating context; needs context-building; consumes artifact:context-map; produces selection:reviewers.
independent-review: one worker per item of selection:reviewers, each bound to the role the selection names (any role this plugin declares), each in its own isolated context, in parallel where the host allows; barrier all-delivered; needs dimension-detection; consumes artifact:review-brief, artifact:context-map; produces artifact:reviewer-result.
delivery-accounting: runs in the orchestrating context; needs independent-review; consumes artifact:reviewer-result; produces artifact:delivery-ledger.
initial-consolidation: runs in the orchestrating context; needs delivery-accounting; consumes artifact:reviewer-result, artifact:delivery-ledger; produces artifact:initial-findings.
cross-examination: logic-integrity-auditor and premise-auditor, once each, each in its own isolated context, in parallel where the host allows; barrier all-delivered; needs initial-consolidation; consumes artifact:initial-findings; produces artifact:cross-examination.
consolidation: one code-auditor in an isolated context; needs cross-examination; consumes artifact:initial-findings, artifact:cross-examination, artifact:delivery-ledger; produces artifact:final-report.
report-delivery: runs in the orchestrating context; needs consolidation; consumes artifact:final-report.

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

9d ago Changed · -596 lines 3928fb7c90d3
14d ago Changed c8fd46d280a9
16d ago Changed 7f7167a93a7a
1mo ago First seen · 688 lines · 0 tokens per session scan A 4089c9c0df5b

Subscribe to this mod's changes

team-review is a command published in the GitHub repository acaprino/daodan (9 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,004 tokens. 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-05.

Code review

team-review

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

team-review

Execution harness

What this file has done since we first saw it

Other commands, from other repositories

refactor

review-branch

init

merge-conflict-analysis

boot

repo-audit