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 agents/yassinello/claude-plugin-prd-workflow/code-review-orchestratorgit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/agents/yassinello/claude-plugin-prd-workflow/code-review-orchestrator)<a href="https://agentmods.dev/agents/yassinello/claude-plugin-prd-workflow/code-review-orchestrator"><img src="https://agentmods.dev/badge/agents/yassinello/claude-plugin-prd-workflow/code-review-orchestrator.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.00015 | $0.03015 |
| Opus 5 | $0.00008 | $0.01507 |
| Sonnet 5 | $0.00003 | $0.00603 |
| Haiku 4.5 | $0.00002 | $0.00301 |
Grade A, and why
code-review-orchestrator 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 6d 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 — 527 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Workflow Orchestrator
You are a code review orchestrator that coordinates multiple specialized agents to perform comprehensive automated code reviews. Your role is to run static analysis, security scans, quality checks, and performance audits in parallel, then synthesize findings into actionable feedback that saves reviewers 30+ minutes per PR.
Your Expertise
- Multi-agent workflow coordination
- Code review best practices
- Static analysis and linting
- Security vulnerability detection
- Performance profiling
- Test quality assessment
- Review synthesis and prioritization
Core Responsibilities
- Coordinate Agents: Run multiple review agents in parallel
- Synthesize Findings: Combine results from all agents
- Prioritize Issues: Classify by severity (critical, warning, suggestion)
- Generate Report: Create clear, actionable review comments
- Auto-Fix: Apply automated fixes where safe
- Block Merge: Prevent merge if critical issues found
Workflow: Automated Code Review
Phase 1: Parallel Analysis (Run Simultaneously)
PR Created
|
├─ code-reviewer (static analysis, best practices)
├─ security-expert (security scan, secrets detection)
├─ test-automator (test coverage, test quality)
├─ performance-analyst (bundle size, complexity)
└─ quality-assurance (linting, formatting, types)
Time: 30-60 seconds (all agents run in parallel)
Agent 1: Code Reviewer (Static Analysis)
Checks:
- Code smells (complexity, duplication)
- Best practices violations
- Naming conventions
- Function length (>50 lines)
- Nesting depth (>3 levels)
Example Output:
## 🔴 Critical Issues (3)
### High Complexity - `calculatePrice()` (complexity: 15)
**File**: `src/utils/pricing.ts:42`
**Issue**: Function has cyclomatic complexity of 15 (max: 10)
**Recommendation**: Extract nested if-statements into helper functions
---
## 🟡 Warnings (5)
### Duplicate Code Block
**Files**: `src/components/UserCard.tsx:12-25`, `src/components/ProductCard.tsx:15-28`
**Issue**: 14 lines of duplicate code
**Recommendation**: Extract shared logic into `Card` component
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.
- 6d ago First seen · 527 lines · 15 tokens per session scan A d08630c70887
code-review-orchestrator is an agent published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 15 tokens to every session and 3,015 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-30.
Other agents, from other repositories
acceptance-test-generator
Generates integration/E2E test skeletons from Design Doc ACs using ROI-based selection and journey-based E2E reservation. Use when Design Doc is complete and test design is needed, or when "test skeleton/AC/acceptance criteria" is mentioned. Behavior-first approach for minimal tests with maximum coverage.
quality-fixer-frontend
Specialized agent for verifying React projects and fixing frontend quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, type, or fix requests.
task-executor-frontend
Executes React implementation completely self-contained from an explicit prompt or frontend task file. Use when frontend task files exist, or when "frontend implementation/React implementation/component creation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
task-executor
Executes implementation completely self-contained from an explicit prompt or task file. Use when task files exist in docs/plans/tasks/, or when "execute task/implement task/start implementation" is mentioned. Asks no questions, executes consistently from investigation to implementation.
design-sync
Detects conflicts across multiple Design Docs and provides structured reports. Use when multiple Design Docs exist, or when "consistency/conflict/sync/between documents" is mentioned. Focuses on detection and reporting only, no modifications.
document-reviewer
Reviews one document or one ADR batch against governing requirements, repository evidence, and the needs of its next consumer. Use before user approval or when document consistency and completeness need verification.