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 skills add poshan0126/dotclaude --skill pr-reviewgit clone --depth 1 https://github.com/poshan0126/dotclaudeWrote 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/poshan0126/dotclaude/pr-review)<a href="https://agentmods.dev/skills/poshan0126/dotclaude/pr-review"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/pr-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.
<a href="https://agentmods.dev/skills/poshan0126/dotclaude/pr-review"><img src="https://agentmods.dev/badge/skills/poshan0126/dotclaude/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.01754 |
| Opus 5.5 | $0.00014 | $0.00702 |
| Sonnet 5.5 | $0.00007 | $0.00351 |
| Haiku 4.5 | $0.00003 | $0.00175 |
Grade A, and why
pr-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 2mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review code changes by delegating to specialist agents in parallel and synthesizing a unified report. Works with PRs, staged changes, or specific files.
Verbosity
Check $ARGUMENTS for the word verbose. Strip it from the argument string before parsing the rest.
- Default: terse output. Each finding is one line (
file:line: issue (fix: hint)). Synthesis report stays compact. verbose: full breakdown. Each finding gets the multi-field block (Severity, Confidence, etc.). Synthesis report uses the full template.
When dispatching reviewers in Step 3, include the word verbose in each Task call's prompt only if the user asked for it. Otherwise omit; the reviewers default to terse.
Step 1: Determine Scope
Parse $ARGUMENTS to determine what to review:
- PR number (e.g.,
123or#123): fetch withgh pr view $ARGUMENTS. This is the full PR review path (includes PR quality checks in Step 2). - No argument: try
gh pr viewto detect a PR for the current branch. If a PR exists, use it. If not, fall back togit diff --cached(staged), thengit diff(unstaged). staged: reviewgit diff --cached. If nothing staged, fall back togit diff.- File path: review that specific file's current state.
If there are no changes to review, say so and stop.
Step 2: PR Quality Check (PR path only)
Skip this step if reviewing staged changes or a file. Jump to Step 3.
When reviewing a PR, fetch and check:
- PR title, description/body, author, base branch, head branch
gh pr diff $NUMBERfor the full diffgh pr checks $NUMBERfor CI statusgh api repos/{owner}/{repo}/pulls/$NUMBER/commentsfor review comments
Review the PR itself before the code:
- Title: descriptive and under 72 chars?
- Description: explains the why? Includes a test plan? Flag if empty or template-only.
- Size: count changed files and lines. Flag if >500 lines changed (suggest splitting).
- Base branch: targeting the right branch?
- CI status: passing, failing, or pending? If failing, note which checks. Fix CI first.
- Unresolved comments: list open review threads with file:line and comment text.
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.
- 2mo ago First seen · 168 lines · 35 tokens per session scan A 851b44527c3e
pr-review is a skill published in the GitHub repository poshan0126/dotclaude (869 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,754 once invoked, about $0.0001 per session on Opus 5.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
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…