ocr

ocr is a skill for Claude Code from spencermarx/open-code-review. It costs 44 tokens per session (2,396 once invoked), scanned A, a copy of ocr, Apache-2.0.

A code-review skill that coordinates several specialised reviewers, each looking at changes from a different perspective, then combines their findings into actionable feedback.

In plain words
What is it for?
It is for reviewing staged changes, commits, branches, pull requests, and implementations against project standards or specifications.
Why use it?
It helps reveal problems in code quality, security, architecture, and testing that one review pass may miss. It also requires a setup check before starting.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions subagents; mentions Claude Code; mentions Codex.

Part of the ocr plugin — 1 skill shipped together

Good fit It is for reviewing staged changes, commits, branches, pull requests, and implementations against project standards or specifications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/spencermarx/open-code-review/ocr
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 spencermarx/open-code-review --skill ocr
Clone the repo
git clone --depth 1 https://github.com/spencermarx/open-code-review

Made for: Claude Code.

Or install ocr, the plugin that ships this one along with the rest of its 1 skill.

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 ocr

README.md
[![agentmods](https://agentmods.dev/badge/skills/spencermarx/open-code-review/ocr/github.svg)](https://agentmods.dev/skills/spencermarx/open-code-review/ocr)
Your own site
<a href="https://agentmods.dev/skills/spencermarx/open-code-review/ocr"><img src="https://agentmods.dev/badge/skills/spencermarx/open-code-review/ocr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for ocr

Your own site · 80×15
<a href="https://agentmods.dev/skills/spencermarx/open-code-review/ocr"><img src="https://agentmods.dev/badge/skills/spencermarx/open-code-review/ocr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,396 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00044 $0.02396
Opus 5.5 $0.00018 $0.00958
Sonnet 5.5 $0.00009 $0.00479
Haiku 4.5 $0.00004 $0.00240

Measured 1mo ago against content hash c2fcb2c62f46, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ocr 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 1mo 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 ocr — 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.

packages/agents/skills/ocr/SKILL.md · 221 lines

How it starts

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

Open Code Review

You are the Tech Lead orchestrating a multi-agent code review. Your role is to coordinate multiple specialized reviewer personas, each examining the code from their unique perspective, then synthesize their findings into actionable feedback.

When to Use This Skill

Activate when the user:

  • Asks to "review my code" or "review these changes"
  • Mentions "code review", "PR review", or "check my implementation"
  • Wants feedback on code quality, security, architecture, or testing
  • Asks to analyze a commit, branch, or pull request

⚠️ IMPORTANT: Setup Guard (Run First!)

Before ANY OCR operation, you MUST validate that OCR is properly set up:

  1. Read and execute references/setup-guard.md
  2. If setup validation fails → STOP and show the user the error message
  3. If setup validation passes → Proceed with the requested operation

This prevents confusing errors and ensures users know how to fix setup issues.

Quick Start

For immediate review of staged changes:

  1. Run the setup guard (see above - this is mandatory!)
  2. Read references/workflow.md for the complete 8-phase process
  3. Begin with Phase 1: Context Discovery
  4. Follow each phase sequentially

Core Responsibilities

As Tech Lead, you must:

  1. Gather Requirements - Accept and analyze any provided specs, proposals, tickets, or context
  2. Discover Context - Load .ocr/config.yaml, pull OpenSpec context, and discover referenced files
  3. Understand Changes - Analyze git diff to understand what changed and why
  4. Evaluate Against Requirements - Assess whether changes meet stated requirements
  5. Identify Risks - Determine which aspects need scrutiny (security, performance, etc.)
  6. Assign Reviewers - Select appropriate reviewer personas based on change type
  7. Facilitate Discourse - Let reviewers challenge each other's findings
  8. Synthesize Review - Produce unified, prioritized, actionable feedback including requirements assessment

Read the full file on GitHub · 221 lines

Files

What ships with it

47 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.

  1. 1mo ago First seen · 221 lines · 44 tokens per session scan A c2fcb2c62f46

Subscribe to this mod's changes

ocr is a skill published in the GitHub repository spencermarx/open-code-review (382 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 44 tokens to every session and 2,396 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to ocr, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

code-reviewer

Review code for best practices, bugs, and security issues.

deepnoodle-ai/dive · 16 tokens

github-review-pr

Review GitHub pull requests with detailed, multi-perspective code analysis using parallel subagents. Use this skill whenever the user wants to review a PR, asks for code review on a pull request, mentions "review PR", "check this PR", "look at pull request", or references a PR number or GitHub PR URL. Do NOT use for…

feiskyer/claude-code-settings · 90 tokens

reviewer

Get a second-opinion review from Google's Antigravity CLI (agy staffer, fast Gemini) - of code (a diff, PR, working tree) or of a decision, plan, or design. Use when the user says /agy:reviewer, "have agy review this", "second opinion on my diff/PR/plan", or after finishing work and wanting an independent verifier…

keli-wen/agy-staff · 94 tokens

generic-fullstack-code-reviewer

Review full-stack code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md compliance. Enforces TypeScript strict mode, input validation, GPU-accelerated animations, and design system consistency. Use when completing features, before commits, or reviewing pull requests.

travisjneuman/.claude · 64 tokens

generic-code-reviewer

Review code for bugs, security vulnerabilities, performance issues, accessibility gaps, and CLAUDE.md workflow compliance. Supports any tech stack - HTML/CSS/JS, React, TypeScript, Node.js, Python, NestJS, Next.js, and more. Use when completing features, before commits, or reviewing pull requests.

travisjneuman/.claude · 70 tokens

bmad-review

Runs one or more installed review lenses — adversarial critique, edge cases, verification gaps, structure, prose — and reports triaged findings. Use when, and only when, the user asks you to review a diff, a pull request, or an artifact — code or documents, one or many — and actually says "review"; an explicit…

alvin-reyes/better-agentic-ide · 117 tokens