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 lexmount/browseruse-agent-bench --skill pr-review-checklistgit clone --depth 1 https://github.com/lexmount/browseruse-agent-benchWrote 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/lexmount/browseruse-agent-bench/pr-review-checklist)<a href="https://agentmods.dev/skills/lexmount/browseruse-agent-bench/pr-review-checklist"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/pr-review-checklist/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/lexmount/browseruse-agent-bench/pr-review-checklist"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/pr-review-checklist.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00077 | $0.00524 |
| Opus 5.5 | $0.00031 | $0.00210 |
| Sonnet 5.5 | $0.00015 | $0.00105 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
pr-review-checklist 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.
What it actually says
PR Review Checklist
Generate PR review checklists into .pr/<pr_number>/ and keep unresolved items current across reruns.
Files
- Script:
scripts/generate_pr_review_checklists.py - Output:
.pr/<pr_number>/review_checklist.md.pr/<pr_number>/unresolved_checklist.md
Prerequisites
- Ensure
ghis installed and authenticated. - Run commands from this skill directory (the directory containing this
SKILL.md). - Set
PYTHONPATHto repo root. - If not authenticated, run
gh auth loginfirst.
Commands
Current branch PR (auto-detect PR number):
export PYTHONPATH=/path/to/browseruse_bench
python3 scripts/generate_pr_review_checklists.py
Specified PR:
export PYTHONPATH=/path/to/browseruse_bench
python3 scripts/generate_pr_review_checklists.py --pr-number 122 --repo lexmount/browseruse-agent-bench
Behavior
- Resolve target PR:
- Use
--pr-numberwhen provided. - Otherwise use current branch PR.
- Use
- Pull review threads and comments from GitHub.
- Render both Markdown files with:
- File + line location
- PR diff hunk snippet
- Current workspace code context near the commented line
- Raw thread chat log (full comment bodies + reply relation)
- Rebuild unresolved checklist on every run.
- Preserve manual checkbox states in
unresolved_checklist.mdfor thread IDs that are still unresolved. - After each successful refresh, explicitly ask the user:
Do you want me to generate/update .pr/<pr_number>/unresolved_solutions.md now?- If yes, run
pr-unresolved-solutionsworkflow immediately.
Notes
- Thread IDs are stable (
TH-<root_comment_id>), suitable for tracking work over time. - For outdated threads, the current code context can differ from PR-time code; rely on diff hunk + thread link together.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 61 lines · 77 tokens per session scan A c6cdfe77f528
pr-review-checklist is a skill published in the GitHub repository lexmount/browseruse-agent-bench (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 77 tokens to every session and 524 once invoked, about $0.0003 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
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
review-readiness
PR readiness dashboard — tracks which reviews have been completed per branch and gates merge decisions. Shows code review, tests, security, QA, and linting status.
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
github
GitHub operations via gh CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available)…
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.