agentmods.dev

repo-native-alignment: Skill for Claude Code

.agents/skills/oh-review/SKILL.md

oh-review is a skill for Claude Code, Codex from open-horizon-labs/repo-native-alignment. It costs 15 tokens per session (1,338 once invoked), scanned A, original, MIT.

A workflow for reviewing a GitHub pull request against the requirements in its linked issue. It produces structured feedback as a GitHub review without changing the code.

In plain words
What is it for?
Use it to inspect an open pull request, find its linked issue, compare the changes with the issue's acceptance criteria, and post review feedback.
Why use it?
It keeps the issue's requirements as the source of truth and helps identify missing or incorrect work before merging. It also checks the repository and pull request context first.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is open-horizon-labs/repo-native-alignment's own configuration. It tells Claude Code and Codex how to work on repo-native-alignment itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything repo-native-alignment configures →

not rated 5repo +1 3d ago A scan 15 tokens original MIT
View source ↗ open-horizon-labs/repo-native-alignment
Reuse

Borrowing it

Nothing to install: this file belongs to open-horizon-labs/repo-native-alignment. 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/open-horizon-labs/repo-native-alignment/main/.agents/skills/oh-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignment

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.

agentmods badge for oh-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-review/github.svg)](https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-review)
Your own site
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-review"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-review/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 oh-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/oh-review"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/oh-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 15 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,338 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 original No closer match found 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.00015 $0.01338
Opus 5 $0.00008 $0.00669
Sonnet 5 $0.00003 $0.00268
Haiku 4.5 $0.00002 $0.00134

Measured 11d ago against content hash 38da5104f8eb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

oh-review 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 11d 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.

.agents/skills/oh-review/SKILL.md · 158 lines

How it starts

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

oh-review

Review a PR, check it against the linked issue's requirements, and post structured feedback as a GitHub review. Read-only except for the review comment itself — no code changes, no commits.

Invocation

/oh-review <pr-number>

  • <pr-number> - the pull request number to review

Prerequisites

  • Repo context: Run from the repo root where the PR exists
  • GitHub CLI: gh must be authenticated

Flow

  1. Load project background from AGENTS.md and relevant .oh/ artifacts. Use RNA repo_map and search first for repository exploration. If RNA is empty or incomplete, broaden queries and remove filters; before any Read/Grep/Bash fallback, document the reason and record a friction event in the repository session context.

  2. Fetch PR metadata:

    gh pr view <pr-number> --json title,body,headRefName,baseRefName,additions,deletions,changedFiles,state,mergeable

    Abort if PR is not open.

  3. Read the linked issue (CRITICAL) — the issue is the source of truth for requirements:

    • Parse "Closes #N" / "Fixes #N" / "Resolves #N" from PR body
    • Fetch the full issue: gh issue view <N> --json title,body
    • Extract acceptance criteria, goal, context, constraints
    • If no linked issue found, note "No linked issue — cannot verify requirements" and review code quality only

  4. Fetch the PR diff:

    gh pr diff <pr-number>

  5. Review the diff against:

    • The linked issue requirements first — are acceptance criteria met? Does the implementation match the goal? Are constraints respected?
    • Code quality (bugs, missing error handling, edge cases)
    • Consistency with existing patterns in the repo
    • Missing tests or documentation

  6. Write a structured review to a temp file:

    ## Review: PR #<number> — <title>

### Requirements Check (from #<issue>)
- [ ] <acceptance criterion 1> — met/not met/partially met
- [ ] <acceptance criterion 2> — met/not met/partially met

### Blockers (P0-P1)
- <issue with explanation and suggested fix>

### Improvements (P2-P3)
- <issue with explanation>

### Clean
- <what looks good>

### Follow-up Work
- <concrete items that should be separate issues/PRs>

Read the full file on GitHub · 158 lines

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. 11d ago First seen · 158 lines · 15 tokens per session scan A 38da5104f8eb

Subscribe to this mod's changes

oh-review is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (5 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 1,338 once invoked, about $0.0001 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-31.

Code reviewGit and workflow
Related

Other skills, from other repositories

review-implement-phase

Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.

prisma/orm · 38 tokens

engram-branch-pr

PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.

Gentleman-Programming/engram · 37 tokens

verify-behavior

Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…

nicknisi/dotfiles · 68 tokens

github-contributor

End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…

daymade/claude-code-skills · 133 tokens

revdiff

Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…

umputun/revdiff · 248 tokens

oss-maintainer

Run an open-source project's issue/PR/release loop like a careful human maintainer — triage to root cause, absorb community PRs before duplicating them, gate every merge, ship honest releases, and thank the people doing your QA for free.

debpalash/VoiceStudio · 55 tokens