Borrowing it
Nothing to install: this file belongs to compozy/kb. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/compozy/kb/main/.agents/skills/cy-review-round/SKILL.mdgit clone --depth 1 https://github.com/compozy/kbWrote 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/skills/compozy/kb/cy-review-round)<a href="https://agentmods.dev/skills/compozy/kb/cy-review-round"><img src="https://agentmods.dev/badge/skills/compozy/kb/cy-review-round.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.00084 | $0.02049 |
| Opus 5 | $0.00042 | $0.01025 |
| Sonnet 5 | $0.00017 | $0.00410 |
| Haiku 4.5 | $0.00008 | $0.00205 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cy-review-round — 100% identical, 0 lines differ
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.
- Derive the PRD directory from the feature name:
-
Identify the review scope.
- Read
_prd.md,_techspec.md, and_tasks.mdfrom the PRD directory to understand what was implemented and why. - Read ADRs from
.compozy/tasks/<name>/adrs/for architectural decision context. - If
_prd.mdand_techspec.mdare 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-onlyto 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
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.
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 · 121 lines · 84 tokens per session scan A 9808c26f113e
cy-review-round is a skill published in the GitHub repository compozy/kb (108 stars, last pushed 16d 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…