browser-use SKILL.md skillB
browser-use from steipete/agent-scripts is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add steipete/agent-scripts/browser-use@git:20260911.866c26dPins git:20260911.866c26d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- steipete/agent-scripts
- Path
skills/browser-use/SKILL.md- Versions recorded
- 8
- Latest version
- git:20260911.866c26d, committed Sep 11, 2026
- First version recorded
- Aug 7, 2026
- Size
- 15,793 bytes
- Repository stars
- 7,386
- License
- MIT
Control the user's existing signed-in Chrome: callable Codex Chrome plugin first, then OpenClaw extension-backed mcporter, with direct DevTools attachment only as a last fallback.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Browser Use Control the user's existing real Chrome profile, especially for login-dependent work and live UI verification. ## Route 1. Use the Codex `Chrome` or `Chrome [Internal]` plugin when it is callable in the active session. Installed on disk is not enough. 2. Otherwise prefer the OpenClaw extension-backed mcporter route. 3. Use legacy direct DevTools attachment only as the explicit last fallback. For mcporter, the MCP call remains the agent-facing control interface. The OpenClaw extension is the transport underneath it, not a separate tool. Set `chromeDevtoolsRelay: "require"` on the canonical global Chrome server definition to enforce relay-only routing. Keep the caller policy explicit as well: ```bash MCPORTER_CHROME_DEVTOOLS_RELAY_POLICY=require mcporter call chrome-devtools.<tool> ``` Seeing an agent request the `chrome-devtools` MCP tool is therefore expected. A Chrome **Allow remote debugging?** prompt or a relay-policy error indicates that the extension transport was not used. The shared daemon retains canonical policy; a shell environment prefix alone cannot change that policy. Never use isolated Chrome, the Codex in-app browser, Playwright, Puppeteer, …
Read the whole file at its exact version.
How to install
mdr add steipete/agent-scripts/browser-use@sha256:b4c648aa84d66539The line at the top of this page pins the label git:20260911.866c26d, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2i2ios4yt7fe7anh)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Aug 7, 2026 and Sep 11, 2026, about one every 5 days. Its first recorded version is graded A and its latest B.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.866c26d latest | 2026-09-11 | 866c26d | 15,793 B | B | view · diff |
| git:20260911.ec388b9 | 2026-09-11 | ec388b9 | 14,959 B | B | view · diff |
| git:20260911.6db16aa | 2026-09-11 | 6db16aa | 14,803 B | A | view · diff |
| git:20260812.2e320ff | 2026-08-12 | 2e320ff | 12,548 B | A | view · diff |
| git:20260812.a6902fe | 2026-08-12 | a6902fe | 12,025 B | A | view · diff |
| git:20260810.587b0dd | 2026-08-10 | 587b0dd | 10,484 B | A | view · diff |
| git:20260809.2cd4d05 | 2026-08-09 | 2cd4d05 | 9,350 B | A | view · diff |
| git:20260807.2469c64 | 2026-08-07 | 2469c64 | 6,967 B | A | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://127.0.0.1:28799)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15793 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
steipete/agent-scripts · 7,386 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2i2ios4yt7fe7anh GET https://markdownregistry.com/api/v1/resolve?ref=steipete/agent-scripts/browser-use GET https://markdownregistry.com/api/v1/blob/b4c648aa84d66539f4cff8704f50e26760c757d5ae8ad7febb08b98a6e45c343
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from steipete/agent-scripts
Every file in steipete/agent-scripts