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 skills/yonatangross/orchestkit/code-review-playbooknpx skills add yonatangross/orchestkit --skill code-review-playbookgit clone --depth 1 https://github.com/yonatangross/orchestkitWrote 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/yonatangross/orchestkit/code-review-playbook)<a href="https://agentmods.dev/skills/yonatangross/orchestkit/code-review-playbook"><img src="https://agentmods.dev/badge/skills/yonatangross/orchestkit/code-review-playbook.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 | $0.00037 | $0.02193 |
| Opus 5 | $0.00018 | $0.01097 |
| Sonnet 5 | $0.00007 | $0.00439 |
| Haiku 4.5 | $0.00004 | $0.00219 |
Grade A, and why
code-review-playbook 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 2d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Playbook
This skill provides a comprehensive framework for effective code reviews that improve code quality, share knowledge, and foster collaboration. Whether you're a reviewer giving feedback or an author preparing code for review, this playbook ensures reviews are thorough, consistent, and constructive.
Overview
- Reviewing pull requests or merge requests
- Preparing code for review (self-review)
- Establishing code review standards for teams
- Training new developers on review best practices
- Resolving disagreements about code quality
- Improving review processes and efficiency
Upstream coverage (do not restate)
This skill is a thin wrapper. General review craft is documented first-party elsewhere;
only OrchestKit's own decisions live here. Load Read("${CLAUDE_PLUGIN_ROOT}/skills/code-review-playbook/references/ork-delta.md")
for the house rules that survived the retired files.
| Topic | Go here instead |
|---|---|
| Review philosophy, speed, tone, PR sizing | https://google.github.io/eng-practices/review/ |
| Conventional comment labels and decorations | references/conventional-comments.md, https://conventionalcomments.org/ |
| OWASP Top 10 review checks | rules/security-baseline.md, https://owasp.org/Top10/ |
| Generic language and framework review checklists | rules/typescript-quality.md, rules/python-quality.md, rules/linting-biome-rules.md |
| Review report shape and multi-agent full-PR review | ork:review-pr |
| Applying findings to the working tree | /code-review --fix, /simplify (see below) |
| Security-only pass over the current branch | /security-review |
| GitHub review mechanics (approve, request changes, inline comments) | https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests |
Conventional Comments
issue [blocking]: Missing error handling for API call
If the API returns a 500 error, this will crash. Add try/catch.
security [blocking]: API endpoint is not authenticated
The /api/admin/users endpoint is missing auth middleware.
What ships with it
16 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.
- assets/pr-template.md 7.1 KB
- examples/conventional-comments.md 2.7 KB
- references/conventional-comments.md 1.7 KB
- references/ork-delta.md 2.8 KB
- rules/_sections.md 1.2 KB
- rules/_template.md 339 B
- rules/linting-biome-rules.md 2.4 KB
- rules/linting-biome-setup.md 1.9 KB
- rules/python-quality.md 3.7 KB
- rules/security-baseline.md 3.8 KB
- rules/typescript-quality.md 3.7 KB
- scripts/fetch-pr-data.sh 7.3 KB runs code
- scripts/review-pr.md 3.5 KB
- scripts/run-lint-check.sh 5.1 KB runs code
- scripts/run-pr-checks.py 14 KB runs code
- test-cases.json 5.1 KB
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.
- 2d ago First seen · 233 lines · 37 tokens per session scan A 1205b09ea7db
code-review-playbook is a skill published in the GitHub repository yonatangross/orchestkit (228 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 2,193 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.
Other skills, from other repositories
code-review-expert
Expert-level code review focusing on quality, security, performance, and maintainability. Use this skill for conducting thorough code reviews, identifying issues, and providing constructive feedback.
add-openagents
Add the OpenAgents Workspace channel so this NanoClaw Agent Group can be driven from an OpenAgents Workspace.
cocotrace
Build and query the SHA-256 requirements-to-implementation traceability graph across lifecycle artifacts.
stage-coach
Consume CocoSentinel per-stage external coach requests and produce stage quality scores.
openagents-workspace
OpenAgents Workspace collaboration tools — shared files, browser, and multi-agent coordination. Use when: sharing files or reports, browsing websites, reading shared files, checking workspace agents, or collaborating with other agents via @mentions.
Agent Workflow Builder
Build multi-agent AI workflows with orchestration, tool use, and state management.