x402 SKILL.md skillA
x402 from browser-use/browser-use is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add browser-use/browser-use/x402@git:20261108.fc47b40Pins git:20261108.fc47b40 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- browser-use/browser-use
- Path
skills/x402/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261108.fc47b40, committed Nov 8, 2026
- First version recorded
- Jun 1, 2026
- Size
- 15,174 bytes
- Repository stars
- 121,725
- License
- MIT
Set up Browser Use Cloud payments with x402 — pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key. Two setups it works out up front — "just use it" (set up a wallet so you or Claude Code can run cloud browser tasks paid from the wallet — Claude writes and runs throwaway scripts, nothing touches your codebase) or "build it in" (install the SDK and write the key + code into your project). Walks through wallet setup, funding, .env, and a ~$1 test run. Use when the…
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 Cloud — pay with x402 (crypto wallet) This is a scripted flow. Follow the steps in order. x402 only works through the **SDK** (`browser-use-sdk` for Python, the `browser-use` npm package for TS) — there is no `browser-use` CLI command for it, so every step runs a short SDK script. ## How to use this script - Lines under **Say:** are spoken to the user **word for word.** Don't paraphrase, add, or drop anything. - `<like this>` inside a Say block is a fill-in — replace it with the real value, keep the rest exact. - Lines under **Ask:** use the AskUserQuestion tool. Use the question and option text exactly as written. - **To show an explanation before a question, put it inside the AskUserQuestion `question` field** (it renders above the options). Don't send it as separate chat text before calling the tool — that text gets dropped when the question UI opens. So: explanation + the actual question both go in the `question` field, in one tool call. - Lines under **Do:** are your actions. Don't read them out. - Track two facts as you go: `SETUP` (A or B, from Step 1) and `MODE` (A or B, from Step 2). …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_kfr5i4m34zlkxgx5/d9b24297e3d60376d2115bb40a3b1d776fa704beccd9d54b8e3a6d9a39abe470.json
Then /plugin install x402@markdownregistry-kfr5i4m34zlkxgx5 in Claude Code. It installs git:20261108.fc47b40, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add browser-use/browser-use/x402@sha256:d9b24297e3d60376The line at the top of this page pins the label git:20261108.fc47b40, 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_kfr5i4m34zlkxgx5)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in browser-use/browser-use/x402 since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of x402 from somewhere else? Ask it: where did my x402 come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Jun 1, 2026 and Nov 8, 2026, about one every 40 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.fc47b40 latest | 2026-11-08 | fc47b40 | 15,174 B | A | view · diff |
| git:20261108.266bca6 | 2026-11-08 | 266bca6 | 15,162 B | A | view · diff |
| git:20260601.fb9af13 | 2026-06-01 | fb9af13 | 15,205 B | A | view · diff |
| git:20260601.23b6ce1 | 2026-06-01 | 23b6ce1 | 15,202 B | A | view · diff |
| git:20260601.6d39576 | 2026-06-01 | 6d39576 | 15,453 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/x402/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15174 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 link to a raw IP address
- pass: No script tag
Source
browser-use/browser-use · 121,725 stars · license MIT · pushed 2026-11-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kfr5i4m34zlkxgx5 GET https://markdownregistry.com/api/v1/resolve?ref=browser-use/browser-use/x402 GET https://markdownregistry.com/api/v1/blob/d9b24297e3d60376d2115bb40a3b1d776fa704beccd9d54b8e3a6d9a39abe470
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 browser-use/browser-use
Every file in browser-use/browser-use