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.
git clone --depth 1 https://github.com/lexmount/browseruse-agent-benchnpx agentmods add skills/lexmount/browseruse-agent-bench/pr-unresolved-solutionsWrote 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-unresolved-solutions)<a href="https://agentmods.dev/skills/lexmount/browseruse-agent-bench/pr-unresolved-solutions"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/pr-unresolved-solutions/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-unresolved-solutions"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/pr-unresolved-solutions.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.00067 | $0.01290 |
| Opus 5.5 | $0.00027 | $0.00516 |
| Sonnet 5.5 | $0.00013 | $0.00258 |
| Haiku 4.5 | $0.00007 | $0.00129 |
Grade A, and why
pr-unresolved-solutions 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PR Unresolved Solutions
Create a scaffold document for unresolved threads, then require the agent to immediately replace placeholders with executable solutions thread-by-thread (without asking for confirmation) and keep checklist states updated while implementing fixes.
Files
- Proposal generator:
scripts/generate_unresolved_solutions.py
- Checklist state sync:
scripts/sync_checklist_status.py
- Resolved section pruner:
scripts/prune_unresolved_solutions.py
- Upstream review thread collector:
../pr-review-checklist/scripts/generate_pr_review_checklists.py
Prerequisites
- Run commands from this skill directory (the directory containing this
SKILL.md). - Set
PYTHONPATHto repo root. - Ensure
.pr/<pr_number>/unresolved_checklist.mdexists. If missing, generate it first.
Commands
- Refresh checklist files from GitHub (optional but recommended):
export PYTHONPATH=/path/to/browseruse_bench
python3 ../pr-review-checklist/scripts/generate_pr_review_checklists.py
- Generate proposal scaffold markdown for unresolved threads (default: current branch PR; fallback: latest
.pr/*):
export PYTHONPATH=/path/to/browseruse_bench
python3 scripts/generate_unresolved_solutions.py
The generator only creates scaffolding placeholders for each thread:
Initial Solution ProposalPlanned ChangesValidation
The agent must replace all AGENT_REQUIRED placeholders with concrete content.
Autonomous Execution Policy (Mandatory)
- After running
generate_unresolved_solutions.py, immediately editunresolved_solutions.mdand fill everyAGENT_REQUIREDplaceholder. - Do not ask the user whether to continue this filling step.
- Ask the user only when a thread is truly blocked by missing product direction, missing access, or conflicting requirements.
- If some threads are blocked, continue filling all other threads first, then report only the blocked
TH-*IDs with clear unblock questions.
Overwrite behavior:
- When
--overwriteis used, existing thread proposals inunresolved_solutions.mdare preserved by default (matched byTH-*). - New unresolved threads are scaffold-only.
- Use
--reset-alltogether with--overwriteonly when you intentionally want to discard all existing proposal content.
What ships with it
3 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.
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 · 147 lines · 67 tokens per session scan A c3a23d3ca516
pr-unresolved-solutions is a skill published in the GitHub repository lexmount/browseruse-agent-bench (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 67 tokens to every session and 1,290 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.