Agent skill

Browser4 Dev

by platonai in platonai/Browser4

Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds.

Apache-2.0Auto-check passedBackend & APIs

Install Browser4 Dev

skills CLI
$ npx skills add platonai/Browser4 --skill browser4-dev -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install platonai/Browser4 browser4-dev --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/platonai/Browser4.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/browser4-dev .claude/skills/browser4-dev && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
browser4-dev
GitHub stars
1.2k
Token cost
~2.2k tokens
SKILL.md length
486 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
Apache-2.0

At a glance

Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds.

  • Works in 10 steps: Add a new CLI command → Add a REST endpoint → Modify browser driver code → …
  • The user asks to add a new browser4-cli command
  • SKILL.md covers Quick Start, When to Use, How It Works and Patterns, plus 5 more sections
  • Calls cargo

What it does

Browser4 Dev is an agent skill from platonai/Browser4. Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds. Use when the user asks to add a new browser4-cli command, new tool domain, REST endpoint, modify Browser4's own Kotlin/Rust code, or check which modules a change affects.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering REST APIs and Android development. It works with Kotlin and Rust. The repository describes itself as: Browser4 — an AI-native browser engine for autonomous agents, intelligent extraction, and large-scale web automation. The licence is Apache-2.0.

When your agent uses it

  • The user asks to add a new browser4-cli command
  • New tool domain
  • Modify Browser4s own Kotlin/Rust code
  • Check which modules a change affects

Example prompts

  • “/browser4-dev”

Requirements

  • Pre-approved tools (allowed-tools): coding.scaffoldFlow, coding.scaffoldFromExample, coding.mvnBuild, coding.devTask, coding.impact, coding.moduleGraph, coding.trapCheck, coding.protect, coding.scaffold, coding.write, coding.read, coding.readLines, coding.replace, coding.replaceRegex, coding.editLines, coding.insertAfter, coding.revert, coding.validate, coding.shell, coding.ktSymbols, coding.ktReferences, coding.ktInheritance, coding.diagnostics, coding.references, coding.symbols, coding.tokenStats, coding.estimateTokens

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Add a new CLI command
  2. Add a REST endpoint
  3. Modify browser driver code
  4. Before changing anything — know the blast radius
  5. Add a new CLI command
  6. Add a new agent tool domain (plugin)
  7. Add a REST endpoint
  8. Add a test class / skill
  9. Clone an existing implementation (anti-staleness)
  10. Plan a whole dev task in one call

What it can do on your machine

Read from SKILL.md and the folder at commit 0fdba82. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • coding.scaffoldFlow
    • coding.scaffoldFromExample
    • coding.mvnBuild
    • coding.devTask
    • coding.impact
    • coding.moduleGraph
    • coding.trapCheck
    • coding.protect
    • coding.scaffold
    • coding.write

    …and 17 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser4 Dev loads about 2.2k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 486 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~96
When it runs · the whole SKILL.md, loaded when a task matches
~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from platonai/Browser4 at commit 0fdba82, republished under its Apache-2.0 licence (© platonai). 486 words, ~2,245 tokens.

Download SKILL.mdSave it as .claude/skills/browser4-dev/SKILL.md (or your agent's skills folder).
name
browser4-dev
description
Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds. Use when the user asks to add a new browser4-cli command, new tool domain, REST endpoint, modify Browser4's own Kotlin/Rust code, or check which modules a change affects.
allowed-tools
coding.scaffoldFlow, coding.scaffoldFromExample, coding.mvnBuild, coding.devTask, coding.impact, coding.moduleGraph, coding.trapCheck, coding.protect, coding.scaffold, coding.write, coding.read, coding.readLines, coding.replace, coding.replaceRegex, coding.editLines, coding.insertAfter, coding.revert, coding.validate, coding.shell, coding.ktSymbols, coding.ktReferences, coding.ktInheritance, coding.diagnostics, coding.references, coding.symbols, coding.tokenStats, coding.estimateTokens
title
browser4-dev
tier
procedure

browser4-dev

Quick Start

Add a new browser4-cli command with one call:

text
coding.scaffoldFlow(type="b4-cli-command", name="my-command", verify=true)

scaffoldFlow generates the whole chain — commands.rs CommandDef, backend MCP alias, tool executor, and test — from a single name; verify=true runs the type-appropriate build check. For other work (agent tool, REST endpoint, test class, skill), use the matching type and see Workflows below.

Develop features inside the Browser4 repository itself, following the repository's own conventions (AGENTS.md) — with multi-file skeletons generated from the repository's real reference implementations, so the output never goes stale.

When to Use

  • User wants to add a new browser4-cli command
  • User wants to add a new agent tool domain (plugin tool)
  • User wants to add a REST endpoint (Controller + Service)
  • User wants to add a test class or a skill
  • User wants to modify Browser4's own Kotlin/Rust code and verify it compiles
  • User wants to know which modules a change affects, or plan a whole dev task

How It Works

scaffoldFlow derives multi-file skeletons from the repository's real reference implementations, so generated code matches current conventions instead of stale templates. moduleGraph/impact rebuild the dependency picture from the live pom.xml files, and mvnBuild verifies with structured diagnostics. Follow AGENTS.md conventions at every step.

Patterns

1. Add a new CLI command
text
coding.scaffoldFlow(type="b4-cli-command", name="my-command", verify=true)
coding.mvnBuild(module="browser4-rest")
2. Add a REST endpoint
text
coding.scaffoldFlow(type="rest-endpoint", name="my-resource", verify=true)
3. Modify browser driver code
text
coding.trapCheck(path="browser4-core/browser4-browser/src/.../PulsarWebDriver.kt")
coding.impact(path=<file>)
coding.mvnBuild(module="browser4-core/browser4-browser")

Flags

coding tools take structured arguments, not CLI flags — see Workflows below for each tool's parameters.

Errors & Recovery

SymptomCauseFix
mvnBuild fails after scaffoldingGenerated code conflicts with existing codeRead diagnostics, fix the conflicting file, re-run
scaffoldFlow rejects verify=trueType-specific build check failedRun without verify, inspect, then re-run after fixing
Unknown blast radiusSkipped moduleGraph/impactRun them first — see Workflow 0

Workflows

0. Before changing anything — know the blast radius
coding.moduleGraph(module="browser4-core/browser4-browser")
  → LIVE module graph rebuilt from the real pom.xml files: direct deps,
    transitive dependents, and drift warnings vs the static snapshot

coding.impact(path="browser4-core/browser4-browser/src/.../PulsarWebDriver.kt")
  → owning module + affected modules (transitively) + suggested test commands

coding.trapCheck(path=<browser-driver file>)
  → CDP pitfall advisories (mouseWheel race, cursor positioning, insertText racing)
1. Add a new CLI command
coding.scaffoldFlow(type="b4-cli-command", name="extract-prices",
     description="Extract product prices from a page", category="Extract")
  → 4 files: commands.rs CommandDef, MCPToolController alias, backend skeleton, test

coding.write(path="cli/browser4-cli/src/commands.rs", content=<CommandDef block>)
coding.write(path="browser4-rest/.../MCPToolController.kt", content=<alias snippet>)
... write each piece ...

# Verify both sides:
coding.shell(command="cargo test --bin browser4-cli")          # Rust side
coding.mvnBuild(module="browser4-rest", goals="compile")       # Kotlin side
Show full SKILL.md (195 more words)Show less
2. Add a new agent tool domain (plugin)
coding.scaffoldFlow(type="agent-tool", name="browser4-weather", domain="weather",
     basePackage="ai.platon.pulsar.weather", toolMethod="fetchWeather",
     description="Fetch weather for the current page")
  → 2 files: ToolExecutor + ToolMount auto-config

coding.mvnBuild(module="browser4-plugins/browser4-weather", goals="compile")
coding.validate(type="plugin", path="browser4-plugins/browser4-weather")
3. Add a REST endpoint
coding.scaffoldFlow(type="rest-endpoint", name="analysis",
     description="Run an analysis task")
  → 3 files: AnalysisController + AnalysisService + AnalysisControllerTest
4. Add a test class / skill
coding.scaffoldFlow(type="test-class", name="my-tool",
     basePackage="ai.platon.pulsar.agentic.tools")
coding.scaffoldFlow(type="skill", name="browser4-myflow",
     description="A custom Browser4 flow")
5. Clone an existing implementation (anti-staleness)
# Single file:
coding.scaffoldFromExample(path="browser4-plugins/browser4-seo/.../SeoToolExecutor.kt")
  → discovery: shows parameters (basePackage, className, domain, toolMethod)
coding.scaffoldFromExample(path=<same>, basePackage="ai.platon.pulsar.weather",
     className="WeatherToolExecutor", domain="weather", toolMethod="fetchWeather")

# Whole plugin directory (cross-file consistent + stem-derived siblings):
coding.scaffoldFromExample(path="browser4-plugins/browser4-seo",
     className="WeatherToolExecutor", basePackage="ai.platon.pulsar.weather",
     domain="weather", artifactId="browser4-weather")
  → renames the executor AND sibling classes sharing the stem
    (SeoAutoConfiguration→WeatherAutoConfiguration, SeoService→WeatherService, ...)
6. Plan a whole dev task in one call
coding.devTask(task="fix the mouseWheel race in PulsarWebDriver.kt under
     browser4-core/browser4-browser/src/main/kotlin, add a regression test",
     verify=true)
  → AGENTS.md dev-flow plan (read → impact → mvnBuild → tests → trapCheck →
    repo-consistency → commit), with the fast checks already RUN:
    compile of the inferred module, CDP trap check, repo-consistency.
    Add runTests=true to also execute the module's test suite.

Rules

  1. Prefer scaffoldFlow over hand-writing — multi-file consistency (same identifier in commands.rs + alias + test) is automatic.
  2. Verify both sides for CLI changes: cargo test --bin browser4-cli for Rust, coding.mvnBuild for Kotlin.
  3. Kotlin diagnostics: use coding.mvnBuild (fast compiler passthrough) — no JDTLS server is configured.
  4. AGENTS.md is the contract — when the repo's conventions change, regenerate skeletons from the updated reference implementations rather than editing stale output.
  5. Keep changes small: one command/domain/endpoint per cycle; coding.revert undoes a bad edit.
  6. Governance files are protected: delete/replace on VERSION, AGENTS.md, CLAUDE.md, root pom.xml, the BOM, and the CI workflow are blocked by design — ask the user for explicit intent instead of working around it. Add session-level protections for any other file with coding.protect(path, on).
  7. Module topology is live: coding.moduleGraph/coding.impact rebuild from the real poms; the static ModuleMap snapshot is guarded by E2E tests against drift — sync it when adding a module. Use coding.ktReferences(scope="module") and coding.ktInheritance before refactoring shared Kotlin symbols.

Examples

User: 给 browser4-cli 加一个 extract-prices 命令
Agent: 1. coding.scaffoldFlow(type="b4-cli-command", name="extract-prices", ...)
       2. 写 commands.rs CommandDef、MCPToolController alias、后端骨架、测试
       3. coding.shell(command="cargo test --bin browser4-cli")
       4. coding.mvnBuild(module="browser4-rest", goals="compile")
       5. 报告:6 处触点全部就位,双端编译通过

User: 克隆 browser4-seo 插件成天气插件
Agent: 1. coding.scaffoldFromExample(path="browser4-plugins/browser4-seo",
          className="WeatherToolExecutor", basePackage="ai.platon.pulsar.weather",
          domain="weather", artifactId="browser4-weather")
       2. 逐文件 coding.write
       3. coding.mvnBuild(module="browser4-plugins/browser4-weather")
       4. coding.validate(type="plugin", path="browser4-plugins/browser4-weather")

© platonai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/browser4-dev of platonai/Browser4.

Open the folder on GitHubat commit 0fdba82

Compare with similar skills

Browser4 Dev next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser4 Dev compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser4 Dev this skillplatonai/Browser41.2k—~2.2kAutomated safety check: PassApache-2.0
Connekt Script WriterAmplicode/spring-skills126—~4.7kAutomated safety check: PassNone
Build Teaql Appteaql/teaql-agent-kit2.8k—~4.6kAutomated safety check: PassMIT
Add Telegram API Actionvendelieu/telegram-bot249—~974Automated safety check: PassApache-2.0
Healthmd CLI QACodyBontecou/health-md230—~4kAutomated safety check: PassAGPL-3.0
Add Property Typeyontrack/yontrack102—~990Automated safety check: PassMIT

Similar skills

  • Connekt Script Writer

    Amplicode/spring-skills

    Write .connekt.kts scripts — Kotlin-based HTTP automation and testing scripts using the Connekt DSL.

    126 GitHub stars~4.7k tokensUpdated 1 mo ago
    Backend & APIsAuto-check passed
  • Build Teaql App

    teaql/teaql-agent-kit

    Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.

    2.8k GitHub stars~4.6k tokensUpdated 11 days ago
    MobileAuto-check passed
  • Add Telegram API Action

    vendelieu/telegram-bot

    Adds a new Telegram Bot API method (action class and top-level functions).

    249 GitHub stars~974 tokensUpdated 3 days ago
    Productivity & AutomationAuto-check passed
  • Healthmd CLI QA

    CodyBontecou/health-md

    Test the standalone Health.md CLI, portable healthmd-mcp server, and direct mobile paths.

    230 GitHub stars~4k tokensUpdated today
    MobileAuto-check passed
  • Add Property Type

    yontrack/yontrack

    Add a complete Yontrack property type — Kotlin PropertyType class, GraphQL mutation provider, and all required frontend UI components (Icon, Display, Form, FormPrepare).

    102 GitHub stars~990 tokensUpdated today
    Backend & APIsAuto-check passed
  • Ktor server patterns including routing DSL, plugins, authentication, Koin DI, kotlinx.serialization, WebSockets, and testApplication testing.

    275k GitHub starsUsed in 4 repos~4.8k tokens
    Backend & APIsAuto-check passed

More from platonai/Browser4

All 17 skills in this repo
  • Data Validation

    platonai/Browser4

    Validates data against common and custom rules (required fields, formats, ranges).

    1.2k GitHub stars~896 tokensUpdated today
    Auto-check passed
  • Form Filling

    platonai/Browser4

    Automatically fills web forms using provided field data and can optionally submit the form.

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Web Scraping

    platonai/Browser4

    Extracts data from web pages using browser automation and CSS/JavaScript selectors.

    1.2k GitHub stars~1.1k tokensUpdated today
    Auto-check passed
  • Organize Task Files

    platonai/Browser4

    Lists, pairs, deduplicates, and moves task files across the Coworker task state machine (0draft → 6git-pushed).

    1.2k GitHub stars~801 tokensUpdated today
    Auto-check passed
  • Task Token Usage

    platonai/Browser4

    Analyzes Claude Code session traces (JSONL) and draft task files to report token usage per task.

    1.2k GitHub stars~701 tokensUpdated today
    Auto-check passed
  • Weather

    platonai/Browser4

    Fetches current weather conditions and a 7-day forecast for a requested location using Open-Meteo geocoding and forecast APIs.

    1.2k GitHub stars~1k tokensUpdated today
    Auto-check passed

Works with

Questions about Browser4 Dev

What does Browser4 Dev do?

Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds. Browser4 Dev is an agent skill from platonai/Browser4. Develop features inside the Browser4 repository itself: add CLI commands, agent tool domains, REST endpoints, tests, and skills; analyze impact, plan dev tasks, check CDP pitfalls, and verify builds.

When should I use Browser4 Dev?

Browser4 Dev fits situations like: the user asks to add a new browser4-cli command; new tool domain; modify Browser4s own Kotlin/Rust code; check which modules a change affects.

How do I install Browser4 Dev in Claude Code?

Run `npx skills add platonai/Browser4 --skill browser4-dev -a claude-code`. Or copy the skill folder (skills/browser4-dev in platonai/Browser4) into .claude/skills/browser4-dev in your project. Claude Code loads it when a task matches its description.

How do I install Browser4 Dev in Codex?

Run `npx skills add platonai/Browser4 --skill browser4-dev -a codex`. Or copy the skill folder (skills/browser4-dev in platonai/Browser4) into .agents/skills/browser4-dev in your project. Codex loads it when a task matches its description.

Can I use Browser4 Dev in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add platonai/Browser4 --skill browser4-dev -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser4-dev, .gemini/skills/browser4-dev, .github/skills/browser4-dev and .opencode/skills/browser4-dev in your project.

What does Browser4 Dev need to run?

Going by SKILL.md and its folder, Browser4 Dev needs the command-line tools its instructions call (cargo). Its frontmatter pre-approves these tools: coding.scaffoldFlow, coding.scaffoldFromExample, coding.mvnBuild, coding.devTask, coding.impact, coding.moduleGraph, coding.trapCheck, coding.protect, coding.scaffold, coding.write, coding.read, coding.readLines, coding.replace, coding.replaceRegex, coding.editLines, coding.insertAfter, coding.revert, coding.validate, coding.shell, coding.ktSymbols, coding.ktReferences, coding.ktInheritance, coding.diagnostics, coding.references, coding.symbols, coding.tokenStats, coding.estimateTokens.

Does Browser4 Dev access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Browser4 Dev safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser4 Dev use?

Browser4 Dev is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Browser4 Dev use?

About 2.2k tokens (SKILL.md is roughly 9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser4 Dev?

Skills that share tags, products or a category with Browser4 Dev: Connekt Script Writer (Amplicode/spring-skills, 126 stars), Build Teaql App (teaql/teaql-agent-kit, 2.8k stars), Add Telegram API Action (vendelieu/telegram-bot, 249 stars) and Healthmd CLI QA (CodyBontecou/health-md, 230 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser4 Dev?

platonai (a GitHub user) maintains it in platonai/Browser4, which has 1,152 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 7, 2026.

Source: platonai/Browser4 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.