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 create-prgit 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/create-pr)<a href="https://agentmods.dev/skills/lexmount/browseruse-agent-bench/create-pr"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/create-pr/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/create-pr"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/create-pr.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.00026 | $0.00564 |
| Opus 5.5 | $0.00010 | $0.00226 |
| Sonnet 5.5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
create-pr 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
Create Pull Request
Create a draft GitHub pull request for this repository using gh.
Prerequisites
ghis installed and authenticated.- Your branch is pushed to origin.
- You are in the repository root.
PR Title Format
Use conventional commit style:
<type>(<scope>): <summary>
Types
feat: New featurefix: Bug fixperf: Performance improvementrefactor: Refactor without behavior changedocs: Documentation onlytest: Tests onlybuild: Build/dependency changesci: CI workflow/config changeschore: Maintenance tasks
Scope Suggestions
corecliagentsbenchmarksdocsskills
Summary Rules
- Imperative present tense (for example:
Add,Fix,Refactor) - Start with capital letter
- No trailing period
- Keep it specific and concise
Workflow
- Inspect local changes:
git status
git diff --stat
git log origin/main..HEAD --oneline
- Decide title components:
- Type
- Scope
- Summary
- Push branch if needed:
git push -u origin HEAD
- Create draft PR:
gh pr create \
--draft \
--base main \
--title "<type>(<scope>): <summary>" \
--body "$(cat <<'PRBODY'
## Summary
- What changed
- Why it changed
## Testing
- [ ] `uv run ruff check .`
- [ ] `uv run pytest`
## Related
- Optional: `closes #<issue-number>`
PRBODY
)"
Body Guidelines
Summary: explain behavior change and key files touched.Testing: list commands actually run.Related: reference GitHub issues when available.
Examples
fix(cli): Propagate skills command exit code
docs(benchmarks): Correct LexBench split filenames
refactor(agents): Guard duplicate agent registration names
Validation Checklist
- Title follows
<type>(<scope>): <summary>. - Summary accurately reflects the patch.
- Testing section contains real commands/results.
- Related issue links are included when relevant.
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 · 125 lines · 26 tokens per session scan A a266059d395a
create-pr is a skill published in the GitHub repository lexmount/browseruse-agent-bench (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 26 tokens to every session and 564 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
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.
github
GitHub API integration via HTTP tool with automatic credential injection.
project-setup
Add a GitHub repository as a tracked project — creates workspace entity, installs workflow automation missions, and includes in dev brief scope.
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.
commit
Generate git commit messages from staged changes.
github-workflow
Install and operate a full GitHub issue-to-merge workflow for any repository using event-driven and cron missions. Handles issue planning, PR monitoring, CI fixing, staging review, and post-merge learning.