docs-update

docs-update is a skill for Claude Code, Codex from lexmount/browseruse-agent-bench. It costs 57 tokens per session (1,012 once invoked), scanned A, original, Apache-2.0.

A workflow for updating Mintlify documentation in the browseruse-bench project. Mintlify is a documentation website system, and this guide covers pages, navigation, links, and matching English and Chinese versions.

In plain words
What is it for?
Use it when adding or editing documentation pages, updating navigation, fixing links, or keeping English and Chinese content in sync.
Why use it?
It helps documentation changes stay consistent across languages and appear correctly in the site's navigation.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when adding or editing documentation pages, updating navigation, fixing links, or keeping English and Chinese content in sync.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lexmount/browseruse-agent-bench/docs-update
Install

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.

Any agent
npx skills add lexmount/browseruse-agent-bench --skill docs-update
Clone the repo
git clone --depth 1 https://github.com/lexmount/browseruse-agent-bench

Made for: Claude Code, Codex.

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.

agentmods badge for docs-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/docs-update/github.svg)](https://agentmods.dev/skills/lexmount/browseruse-agent-bench/docs-update)
Your own site
<a href="https://agentmods.dev/skills/lexmount/browseruse-agent-bench/docs-update"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/docs-update/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.

agentmods 80×15 button for docs-update

Your own site · 80×15
<a href="https://agentmods.dev/skills/lexmount/browseruse-agent-bench/docs-update"><img src="https://agentmods.dev/badge/skills/lexmount/browseruse-agent-bench/docs-update.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,012 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00057 $0.01012
Opus 5.5 $0.00023 $0.00405
Sonnet 5.5 $0.00011 $0.00202
Haiku 4.5 $0.00006 $0.00101

Measured 1mo ago against content hash cd14df4b081c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

browseruse_bench/skills/docs-update/SKILL.md · 121 lines

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 (en and zh),
  • 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/...
  • API Reference:
    • English: docs/api-reference/... or docs/en/api-reference/... (follow existing repo convention)
    • Chinese: docs/zh/api-reference/...
  • Assets:
    • Images/icons: docs/images/...
    • Logos: docs/logo/...
    • Favicon: usually docs/favicon.svg

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 .mdx and update references.
  • docs/docs.json page 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 title and description.
  • Use icon only when section convention already uses icons.
  • Keep descriptions concise and meaningful for search/snippets.

5. Bilingual parity rules (en / zh)

  • For each new en page, add a matching zh page 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.

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

  1. 1mo ago First seen · 121 lines · 57 tokens per session scan A cd14df4b081c

Subscribe to this mod's changes

docs-update is a skill published in the GitHub repository lexmount/browseruse-agent-bench (20 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,012 once invoked, about $0.0002 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.