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/spencermarx/open-code-review/ocrnpx skills add spencermarx/open-code-review --skill ocrgit clone --depth 1 https://github.com/spencermarx/open-code-reviewWrote 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/spencermarx/open-code-review/ocr)<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="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.00044 | $0.02396 |
| Opus 5 | $0.00022 | $0.01198 |
| Sonnet 5 | $0.00009 | $0.00479 |
| Haiku 4.5 | $0.00004 | $0.00240 |
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 yesterday.
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.
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.
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:
- Read and execute
references/setup-guard.md - If setup validation fails → STOP and show the user the error message
- 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:
- Run the setup guard (see above - this is mandatory!)
- Read
references/workflow.mdfor the complete 8-phase process - Begin with Phase 1: Context Discovery
- Follow each phase sequentially
Core Responsibilities
As Tech Lead, you must:
- Gather Requirements - Accept and analyze any provided specs, proposals, tickets, or context
- Discover Context - Load
.ocr/config.yaml, pull OpenSpec context, and discover referenced files - Understand Changes - Analyze git diff to understand what changed and why
- Evaluate Against Requirements - Assess whether changes meet stated requirements
- Identify Risks - Determine which aspects need scrutiny (security, performance, etc.)
- Assign Reviewers - Select appropriate reviewer personas based on change type
- Facilitate Discourse - Let reviewers challenge each other's findings
- Synthesize Review - Produce unified, prioritized, actionable feedback including requirements assessment
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.
- AGENTS.md 2.0 KB
- assets/config.yaml 8.6 KB
- assets/ocr-gitignore 113 B
- assets/reviewer-template.md 2.1 KB
- references/context-discovery.md 5.2 KB
- references/discourse.md 4.6 KB
- references/final-template.md 14 KB
- references/map-agent-task.md 5.9 KB
- references/map-personas/architect.md 3.3 KB
- references/map-personas/flow-analyst.md 3.2 KB
- references/map-personas/requirements-mapper.md 3.8 KB
- references/map-template.md 6.9 KB
- references/map-workflow.md 21 KB
- references/reviewer-task.md 7.7 KB
- references/reviewers/accessibility.md 3.1 KB
- references/reviewers/ai.md 3.2 KB
- references/reviewers/anders-hejlsberg.md 4.1 KB
- references/reviewers/architect.md 3.1 KB
- references/reviewers/backend.md 2.8 KB
- references/reviewers/data.md 3.2 KB
- references/reviewers/devops.md 3.2 KB
- references/reviewers/docs-writer.md 4.3 KB
- references/reviewers/dx.md 3.0 KB
- references/reviewers/frontend.md 2.9 KB
- references/reviewers/fullstack.md 3.1 KB
- references/reviewers/infrastructure.md 3.0 KB
- references/reviewers/john-ousterhout.md 3.8 KB
- references/reviewers/kamil-mysliwiec.md 4.3 KB
- references/reviewers/kent-beck.md 3.7 KB
- references/reviewers/kent-dodds.md 4.5 KB
- references/reviewers/martin-fowler.md 3.9 KB
- references/reviewers/mobile.md 3.3 KB
- references/reviewers/performance.md 3.1 KB
- references/reviewers/principal.md 2.2 KB
- references/reviewers/quality.md 2.4 KB
- references/reviewers/reliability.md 3.2 KB
- references/reviewers/rich-hickey.md 4.6 KB
- references/reviewers/sandi-metz.md 4.4 KB
- references/reviewers/security.md 2.5 KB
- references/reviewers/staff-engineer.md 3.2 KB
- references/reviewers/tanner-linsley.md 4.3 KB
- references/reviewers/testing.md 2.3 KB
- references/reviewers/vladimir-khorikov.md 4.3 KB
- references/session-files.md 9.9 KB
- references/session-state.md 13 KB
- references/setup-guard.md 4.6 KB
- references/workflow.md 38 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.
- yesterday First seen · 221 lines · 44 tokens per session scan A c2fcb2c62f46
ocr is a skill published in the GitHub repository spencermarx/open-code-review (353 stars, last pushed 1mo 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. 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.
Other skills, from other repositories
glossary-init
USE WHEN setting up a repo for AI-first work, when an agent hallucinates domain term meaning, or when user asks to bootstrap / extend the repo's domain glossary. Surfaces candidate terms by identifier frequency, asks the user for 1-sentence definitions, writes GLOSSARY.md at repo root. Idempotent — re-running adds new…
codex-pair-resume
Resume codex-pair for this project after a previous pause. Removes .codex-pair/state/paused and clears failure state. Review resumes on the next supported file edit; missing state is a no-op.
generate-tests
Generate unit tests for a .NET service following the coverage-kit conventions. Use when the user asks to 'generate tests', 'backfill tests', 'characterize this service', or 'add tests for' a target after coverage-init has run. Operates in characterization mode (freeze current behavior for existing code) or spec mode…
conventions-init
USE WHEN setting up a repo for AI-first work (after /init-repo), or when the context-surface hook should start feeding repo conventions to agents before edits. Drafts conventions.yml at repo root: per-kind casing (inferred from the code), a vague-name denylist seed, directory roles, and a hand-filled house-rules…
opik
This skill should be used when the user needs to add Opik tracing or integrations to their code, instrument an LLM application, or needs reference for Opik SDK usage (Python, TypeScript, REST API). Use for tasks like "add tracing", "instrument my code", "use trackopenai", "add OpikTracer", "what span types are…
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…