code-review-orchestration

code-review-orchestration is a skill for Claude Code from a5c-ai/babysitter. It costs 31 tokens per session (392 once invoked), scanned A, original, MIT.

A coordinated code-review process that examines changes from several viewpoints, including architecture, security, performance, testing, code quality, and documentation. It combines the findings into a weighted score and recommendation.

In plain words
What is it for?
Use it for pre-merge reviews, post-implementation checks, and quality gates in a feature workflow.
Why use it?
It helps catch different kinds of problems that one review may miss. The scoring rules provide a consistent basis for approving changes or requesting fixes before merging.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it for pre-merge reviews, post-implementation checks, and quality gates in a…

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/a5c-ai/babysitter/code-review-orchestration
About the project

Babysitter is a workflow engine for AI coding agents that enforces predefined steps, quality checks, human approvals, and decision records. It is used to coordinate complex, repeatable agent workflows across supported coding tools. The catalogue contains skills, agents, instructions, settings, a plugin, and an MCP integration for its workflow.

a5c-ai/babysitter · 1,772 stars · on GitHub · a5c.ai

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 a5c-ai/babysitter --skill code-review-orchestration
Clone the repo
git clone --depth 1 https://github.com/a5c-ai/babysitter

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 code-review-orchestration

README.md
[![agentmods](https://agentmods.dev/badge/skills/a5c-ai/babysitter/code-review-orchestration.svg)](https://agentmods.dev/skills/a5c-ai/babysitter/code-review-orchestration)
Your own site
<a href="https://agentmods.dev/skills/a5c-ai/babysitter/code-review-orchestration"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/code-review-orchestration.svg" alt="Measured on agentmods" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 392 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.00031 $0.00392
Opus 5 $0.00015 $0.00196
Sonnet 5 $0.00006 $0.00078
Haiku 4.5 $0.00003 $0.00039

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

Security

Grade A, and why

code-review-orchestration 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 3d 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.

library/methodologies/claudekit/skills/code-review-orchestration/SKILL.md · 51 lines

What it actually says

Scoring and Recommendation

  • APPROVE: overall >= 80 AND zero critical issues
  • REQUEST_CHANGES: overall >= 60 OR has critical issues
  • REJECT: overall < 60

When to Use

  • /code-review slash command
  • Post-implementation review in spec execution
  • Pre-merge quality gate

Agents Used

  • code-review-coordinator, security-analyst, performance-analyst
  • testing-specialist, architecture-reviewer

Processes Used By

  • claudekit-code-review (primary consumer)
  • claudekit-orchestrator (via command dispatch)
Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 3d ago First seen · 51 lines · 31 tokens per session scan A e8a9d8b910f3

Subscribe to this mod's changes

code-review-orchestration is a skill published in the GitHub repository a5c-ai/babysitter (1,772 stars, last pushed yesterday), licensed MIT. It adds 31 tokens to every session and 392 once invoked, about $0.0002 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-09-03.