What is cy-review-round?

A review workflow skill that examines an implemented product requirement and writes a numbered set of new issue files for a later fixing process.

Use it to audit a completed feature, create a new review round, and record only previously untracked problems.

It keeps review findings organized and avoids reporting issues that were already recorded in earlier review rounds.

How compozy/skeeper configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to compozy/skeeper. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/compozy/skeeper/main/.agents/skills/cy-review-round/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/compozy/skeeper

Made for: Claude Code, Codex.

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/skills/compozy/skeeper/cy-review-round.svg)](https://agentmods.dev/skills/compozy/skeeper/cy-review-round)

Your own site

<a href="https://agentmods.dev/skills/compozy/skeeper/cy-review-round"><img src="https://agentmods.dev/badge/skills/compozy/skeeper/cy-review-round.svg" alt="Measured on agentmods" height="20"></a>

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,049 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 100% copy Near-identical to another mod 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.00084	$0.02049
Opus 5	$0.00042	$0.01025
Sonnet 5	$0.00017	$0.00410
Haiku 4.5	$0.00008	$0.00205

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

Security

Grade A, and why

cy-review-round 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 7d 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.

Origin

This is a copy

100% identical to cy-review-round — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/cy-review-round/SKILL.md · 121 lines

How it starts

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

Review Round

Perform a structured code review of a PRD implementation and produce a review round directory that the cy-fix-reviews workflow can process.

Required Inputs

Feature name identifying the .compozy/tasks/<name>/ directory.
Optional: specific files or directories to scope the review.

Workflow

Determine the review round directory.
- Derive the PRD directory from the feature name: .compozy/tasks/<name>/.
- Verify the PRD directory exists. If it does not, stop and report the missing directory.
- List existing reviews-NNN/ subdirectories to determine the next round number. If none exist, use round 1.
- If prior review rounds exist, read their issue files to build a list of already-known issues. The current round must only contain NEW issues not already tracked in prior rounds. Do not re-flag issues that are pending, valid, or resolved in earlier rounds.
- Determine the review round directory path: .compozy/tasks/<name>/reviews-NNN/ with the round number zero-padded to 3 digits. Do NOT create it yet — wait until step 4 confirms there are issues to write. This avoids leaving empty directories when the review finds no issues.
Identify the review scope.
- Read _prd.md, _techspec.md, and _tasks.md from the PRD directory to understand what was implemented and why.
- Read ADRs from .compozy/tasks/<name>/adrs/ for architectural decision context.
- If _prd.md and _techspec.md are both missing, warn that the review will lack requirements context but proceed with a code-quality-only review.
- If the user provided specific files or directories, scope the review to those paths.
- If no explicit scope was provided, run git diff main...HEAD --name-only to discover all files created or modified on the current branch. If the diff is empty or unhelpful, ask the user to specify files.
- Spawn an Agent tool call to explore the identified files, their imports, and their dependencies to build a map of the implementation.

Read the full file on GitHub · 121 lines

Files

What ships with it

2 files 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.

7d ago First seen · 121 lines · 84 tokens per session scan A 9808c26f113e

Subscribe to this mod's changes

cy-review-round is a skill published in the GitHub repository compozy/skeeper (85 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 2,049 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cy-review-round, differing in 0 lines, and is treated as a copy.

Code review

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

rework-rate

Measure and interpret PR rework rate — the emerging 5th DORA metric.

bradygaster/squad · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 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

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens

skeeper: Skill for Claude Code