browser SKILL.md skillB
browser from shibing624/agentica is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shibing624/agentica/browser@v1.0Pins v1.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shibing624/agentica
- Path
agentica/skills/bundled/browser/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0, committed Nov 8, 2026
- Size
- 4,828 bytes
- Repository stars
- 365
- License
- Apache-2.0
Drive a real or headless browser from the shell to verify web UI changes, click through flows, inspect console/network errors, or act inside the user's logged-in Chrome/Edge session. Use when fetch_url is not enough — SPAs, localhost dev servers, form interactions, visual checks, or authenticated sites (via agent-browser, lightpanda, bsk BrowserSkill, or playwright-cli).
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 automation from the shell There is no dedicated browser tool in the schema on purpose: browser CLIs keep a warm daemon between shell calls and cost zero tool-schema tokens on turns that do not touch a browser. Drive them through `execute`. If you only need to read a public static page, use `fetch_url` first. Reach for a browser when the page needs JavaScript, you are verifying a UI you just edited, or the task requires clicking, filling forms, screenshots, or the user's existing login state. ## 1. Pick the right driver Probe what is installed before your first call (`command -v agent-browser bsk lightpanda playwright-cli`): | Task | Tool to use | Why | |---|---|---| | **Local dev preview (`localhost`), UI verification, public interactive pages** | `agent-browser` (default) | Fast Rust CLI + background daemon; `snapshot -i` returns compact `@e1` refs | | **Fast read-only extraction on JS/SSR pages (no pixels needed)** | `agent-browser --engine lightpanda` or `lightpanda fetch --dump markdown <url>` | Zig engine, ~10x faster cold start and ~16x less memory than Chrome; no screenshots or extensions | …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_pin5tsw42bfzhe2x/6bf99fe68a90bbcdf6b0591ebb0f3482112784e4617fcf8c738b5e9555c8a18d.json
Then /plugin install browser@markdownregistry-pin5tsw42bfzhe2x in Claude Code. It installs v1.0, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add shibing624/agentica/browser@sha256:6bf99fe68a90bbcdThe line at the top of this page pins the label v1.0, 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_pin5tsw42bfzhe2x)
4 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 shibing624/agentica/browser 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 browser from somewhere else? Ask it: where did my browser 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 1 version of this file, committed on Nov 8, 2026.
Watch this file (sign in, one email per new version)
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/browser/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
- fail: No link to a raw IP address (matched: http://127.0.0.1:8881)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4828 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
shibing624/agentica · 365 stars · license Apache-2.0 · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pin5tsw42bfzhe2x GET https://markdownregistry.com/api/v1/resolve?ref=shibing624/agentica/browser GET https://markdownregistry.com/api/v1/blob/6bf99fe68a90bbcdf6b0591ebb0f3482112784e4617fcf8c738b5e9555c8a18d
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 shibing624/agentica
Every file in shibing624/agentica