An automated check for a pull-request review, meaning a review of proposed code changes before they are merged. It runs the review and verifies every required rule in an invariants file.

It helps build the review tool, run a review or preview, and validate the finished review across its required checks and supported environments.

It prevents review guarantees from being skipped or checked informally. A failed or incomplete verification is reported rather than treated as successful.

acceptance — Skill for Claude Code by guimatheus92

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/guimatheus92/pr-review

agentmods

npx agentmods add skills/guimatheus92/pr-review/acceptance

Made for: Claude Code.

Or install pr-review, the plugin that ships this one along with the rest of its 3 skills, 1 command.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/guimatheus92/pr-review/acceptance/github.svg)](https://agentmods.dev/skills/guimatheus92/pr-review/acceptance)

Your own site

<a href="https://agentmods.dev/skills/guimatheus92/pr-review/acceptance"><img src="https://agentmods.dev/badge/skills/guimatheus92/pr-review/acceptance/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/guimatheus92/pr-review/acceptance"><img src="https://agentmods.dev/badge/skills/guimatheus92/pr-review/acceptance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,262 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.

Model	Per session	Once invoked
Fable 5.1	$0.00080	$0.01262
Opus 5	$0.00040	$0.00631
Sonnet 5	$0.00016	$0.00252
Haiku 4.5	$0.00008	$0.00126

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

Security

Grade A, and why

acceptance 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 3d 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.

.claude/skills/acceptance/SKILL.md · 100 lines

How it starts

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

Testing a PR review

The checklist is a program, not prose. pr-review verify renders one row per invariant in INVARIANTS.md, always the full list, and exits 2 on any FAIL — so there is no version of this task where an item gets skipped by accident. Your job is the judgment: read the FAIL rows, find out why, report honestly.

Do not hand-check the guarantees. If you find yourself reading a PR in the browser to see whether a comment is inline, you have left the deterministic path. Fix the check instead.

Steps

Run these in order. Do not skip a step because the previous one looked fine.

Build. npm run build verify and the matrix drive dist/cli.cjs, not src/. A stale bundle audits code that is not the code under test.

Review the PR.

node dist/cli.cjs review <pr-url>            # posts
node dist/cli.cjs review <pr-url> --dry-run  # previews

Long runs: add --detach and poll node dist/cli.cjs status <run-id>.

Audit it.
```
node dist/cli.cjs verify --pr <pr-url>
```
Exit 0 = every invariant PASS or SKIP. Exit 1 = the audit could not be completed (the PR read-back failed) — report that as "not verified", never as "clean". Exit 2 = at least one FAIL, and a FAIL is a product defect until proven otherwise. --offline skips the live PR read on purpose (every row that needs it reports SKIP, and the exit stays 0); --json for machine use.
The matrix — all three providers, every time.
```
npm run acceptance                    # 3 providers x 2 runtimes + the file-list and no-fetch gates
```
GitHub alone is not a result. Azure DevOps and GitLab have full providers and zero non-stubbed coverage anywhere else in this repo, so a matrix narrowed to --provider github proves the one path that was already proven. Narrow it only to re-run a single failing cell while fixing it, and re-run the whole thing before you call the work done.

Read the full file on GitHub · 100 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.

3d ago First seen · 100 lines · 80 tokens per session scan A 6899a8cb5167

Subscribe to this mod's changes

acceptance is a skill published in the GitHub repository guimatheus92/pr-review (2 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 1,262 once invoked, about $0.0004 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-08.

Claude Code Code review E2E testing Testing ai-agents automation azure-devops cli

include-test-files-that-assert-on-behavior-being-changed-in-decl

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 29 tokens

e2e

Generate and run Playwright E2E tests traced to spec.md acceptance criteria, with an optional accessibility audit. Use when saying "e2e tests" or "a11y audit".

anton-abyzov/specweave · 38 tokens

auto-canary

A deployment health-check skill for testing whether a recently deployed or staging website is working. It runs build, end-to-end, and browser checks, then reports a pass, warning, or failure.

Insajin/autopus-adk · 24 tokens

simulate-agents

Run Mock User and Auditor agents against a feature in fresh contexts before human review. Use after verify-work, before request-review, when user wants pre-review simulation.

danielvm-git/bigpowers · 36 tokens

testing-strategy

A testing guide that explains how to combine unit, integration, contract, and end-to-end tests. End-to-end tests check complete user flows, while integration tests check components working together.

Insajin/autopus-adk · 20 tokens

qawolf-cli

Manage QA Wolf through the qawolf CLI. Use when asked to create, update, or list coverage requests, bug reports, or maintenance reports; start a run of flows or tags on the QA Wolf platform or read a run's results; list, set, or delete environment variables; manage environments, flows, or tags; request automation of…

qawolf/cli · 118 tokens