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/platonai/browser4/browser4-fix-bugnpx skills add platonai/Browser4 --skill browser4-fix-buggit clone --depth 1 https://github.com/platonai/Browser4What 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.00078 | $0.01568 |
| Opus 5 | $0.00039 | $0.00784 |
| Sonnet 5 | $0.00016 | $0.00314 |
| Haiku 4.5 | $0.00008 | $0.00157 |
Grade A, and why
browser4-fix-bug 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 3d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
browser4-fix-bug
Quick Start
coding.shell(command="mvn -pl <module> -am compile -DskipTests") # 1. reproduce the error
coding.readLines(path=<file>, startLine=<line-8>, endLine=<line+8>) # 2. read the failing code
coding.replace(path=<file>, old="...", new="...") # 3. smallest possible edit
coding.shell(command="mvn -pl <module> -am compile -DskipTests") # 4. re-verify until green
Drive a bug from "it fails" to "it passes" with a disciplined compile-test-fix loop. Never guess — read the actual error, make the smallest edit, and re-verify.
When to Use
- User reports a build/compile failure or a failing test
- A plugin, skill script, JS, or shell script errors at runtime
- User says "fix this error", "the build is broken", "tests fail", "it crashes"
- LSP diagnostics (
coding.diagnostics) report errors in a file
How It Works
The compile-test-fix loop is error-driven: reproduce the failure, read the exact error, locate the faulty lines with minimal context, make the smallest possible edit, and re-verify. Never guess — every iteration starts from the actual error output.
Patterns
1. Build/compile failure
coding.shell(command="mvn -pl <module> -am compile -DskipTests")
coding.readLines(path=<file>, startLine=<line-8>, endLine=<line+8>)
coding.replace(path=<file>, old="...", new="...")
coding.shell(command="mvn -pl <module> -am compile -DskipTests")
2. Failing test
coding.shell(command="mvn test -pl <module> -Dtest=<TestClass>")
coding.readLines(path=<test-file>, startLine=<line-8>, endLine=<line+8>)
coding.replace(path=<file>, old="...", new="...")
3. Runtime error in plugin/script
coding.diagnostics(path=<file>)
coding.readLines(path=<file>, startLine=<line-8>, endLine=<line+8>)
coding.replace(path=<file>, old="...", new="...")
Flags
coding tools take structured arguments, not CLI flags — see Workflow below for each tool's parameters.
Errors & Recovery
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.
- 3d ago First seen · 143 lines · 78 tokens per session scan A 34f7088d7f07
browser4-fix-bug is a skill published in the GitHub repository platonai/Browser4 (1,114 stars, last pushed 4d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,568 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.
Other skills, from other repositories
eric-task-master
Install, connect, and use Eric Task Master for durable Playwright browser jobs with persistent or ephemeral Profiles, live fast-auto-human behavior control, task queues, progress health, semantic diagnostics, recovery, artifacts, and composable Task Packs.
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".