browser4-dev

A development guide for Browser4, a repository containing browser tools and related code. It covers adding command-line commands, agent tools, web endpoints, tests, and changes to the project's Kotlin or Rust code.

In plain words
What is it for?
Use it to plan or implement Browser4 features, generate multi-file starting points, add tests or skills, and check that changes compile.
Why use it?
Adding one feature in a large repository can require coordinated changes across several files and modules. It helps identify the affected parts and follow Browser4's existing development patterns.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/platonai/browser4/browser4-dev
Any agent
npx skills add platonai/Browser4 --skill browser4-dev
Clone the repo
git clone --depth 1 https://github.com/platonai/Browser4

Made for: Claude Code, Codex.

Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,160 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00084 $0.02160
Opus 5 $0.00042 $0.01080
Sonnet 5 $0.00017 $0.00432
Haiku 4.5 $0.00008 $0.00216

Measured yesterday against content hash 4c1fc7222360, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

browser4-dev 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 yesterday.

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.

skills/browser4-dev/SKILL.md · 203 lines

How it starts

The opening of the file, as written. The whole thing — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.

browser4-dev

Quick Start

Add a new browser4-cli command with one call:

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

coding.scaffoldFlow(type="b4-cli-command", name="my-command", verify=true)
coding.mvnBuild(module="browser4-rest")

2. Add a REST endpoint

coding.scaffoldFlow(type="rest-endpoint", name="my-resource", verify=true)

3. Modify browser driver code

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.

Read the full file on GitHub · 203 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. yesterday First seen · 203 lines · 84 tokens per session scan A 4c1fc7222360

Subscribe to this mod's changes

browser4-dev is a skill published in the GitHub repository platonai/Browser4 (1,114 stars, last pushed 2d ago), licensed Apache-2.0. It adds 84 tokens to every session and 2,160 once invoked, about $0.0004 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.