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 agentmods add skills/lexmount/browseruse-agent-bench/docs-updatenpx skills add lexmount/browseruse-agent-bench --skill docs-updategit clone --depth 1 https://github.com/lexmount/browseruse-agent-benchWhat 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 | $0.00057 | $0.01012 |
| Opus 5 | $0.00028 | $0.00506 |
| Sonnet 5 | $0.00011 | $0.00202 |
| Haiku 4.5 | $0.00006 | $0.00101 |
Grade A, and why
docs-update 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 2d 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Update
Use this workflow to create or update Mintlify docs under docs/, including:
- site-level setup (
docs/docs.json, theme, branding), - bilingual content parity (
enandzh), - navigation consistency and link correctness.
If user asks for "Mintlify style docs", this skill is sufficient for most cases. Use official Mintlify docs only when syntax/fields are unclear or a new feature is requested.
1. Identify update type first
- Page-only update: Content changes only; update paired language page and navigation if needed.
- Section update: Add/rename groups and pages in both languages.
- Site bootstrap/update: Create or update
docs/docs.json, logo/favicon paths, navbar/footer, tabs.
2. Standard directory layout
- Guides and general docs:
- English:
docs/en/... - Chinese:
docs/zh/...
- English:
- API Reference:
- English:
docs/api-reference/...ordocs/en/api-reference/...(follow existing repo convention) - Chinese:
docs/zh/api-reference/...
- English:
- Assets:
- Images/icons:
docs/images/... - Logos:
docs/logo/... - Favicon: usually
docs/favicon.svg
- Images/icons:
Prefer matching existing project conventions; do not mix two API reference layouts in one repo.
3. Enforce .mdx pages
- All content pages must be
.mdx. - If a page exists as
.md, rename to.mdxand update references. docs/docs.jsonpage paths must omit file extensions.
4. Frontmatter baseline (required)
Every content page should start with:
---
title: "Page Title"
description: "Short summary of this page"
icon: "optional-icon"
---
Rules:
- Localize
titleanddescription. - Use
icononly when section convention already uses icons. - Keep descriptions concise and meaningful for search/snippets.
5. Bilingual parity rules (en / zh)
- For each new
enpage, add a matchingzhpage at the same relative path. - Keep group structure and page order aligned across languages.
- If translation is not ready, add a localized placeholder page:
- Chinese placeholder:
该页面正在翻译中。 - English placeholder:
This page is pending translation.
- Chinese placeholder:
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.
- 2d ago First seen · 121 lines · 57 tokens per session scan A cd14df4b081c
docs-update is a skill published in the GitHub repository lexmount/browseruse-agent-bench (19 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,012 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
agent-browser
Browse the web for any task — research topics, read articles, interact with web apps, fill forms, take screenshots, extract data, and test web pages. Use whenever a browser would be useful, not just when the user explicitly asks.
dingtalk_channel_connect
Use a headed browser to automatically complete DingTalk channel integration for QwenPaw. Applicable when the user mentions DingTalk, developer console, Client ID, Client Secret, bot, Stream mode, binding or configuring a channel. Supports pausing when a login page is detected and resuming after the user logs in.
browser_cdp
当用户明确希望连接到已运行的 Chrome 浏览器、扫描本地 CDP 端口、显式指定 cdpport，或让多个 agent / 工具共享同一个浏览器时，使用本 skill。browser 默认不开放调试端口；仅当用户明确希望其他本地工具附加时才显式传入 cdpport。.
browser_visible
当用户需要控制 browser 的浏览器启动方式时，使用本 skill。browser 默认由 Playwright 直接管理、不开放调试端口（需让其他本地工具附加时显式传 cdpport）；headed 控制是否显示窗口，privatemode 保留用于兼容、不再改变默认行为，browserargs 传入额外的 Chromium 启动参数，executablepath 指定自定义浏览器可执行文件路径。.
browser_visible
Use this skill when the user needs to control the browser launch mode for browser. By default browser is managed by Playwright and opens no debugging port (pass an explicit cdpport to let another local tool attach); headed controls whether the window is visible, and privatemode is kept for backward compatibility and…
browser
Drive a live browser with async Python against QwenPaw's builtin Browser SDK. The full reference is below; re-load this browser skill after context compaction.