browser-automation is agent-read markdown (skill) from jnpiyush/agentx: Drive a real browser from an Frontier FDE for prototype validation, web research, HTML output verification, and accessibility audits. Use when an agent needs to render JavaScript, click/type/screenshot a page, run an axe-core a11y audit, or read a JS-rendered page. Backed by Microsoft's Playwright MCP server (transport decided in ADR-342). Local-first, opt-in install..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Browser Automation
> **When to load**: An Frontier FDE needs to render a page in a real browser, interact with it, capture a screenshot, run an accessibility audit, or read JavaScript-rendered content. Most commonly: UX Designer validating prototypes, Consulting Research reading SPAs, Engineer doing quick end-to-end smoke checks.
> **DEFAULT test surface for UI-bearing changes**: Per the always-on rule in
> `.github/instructions/project-conventions.instructions.md`, the agent browser
> is the DEFAULT testing surface whenever a change renders UI or HTML. The
> expected pass: render the running build, capture a snapshot/screenshot per
> primary route, run an axe-core a11y scan, and drive at least one scripted
> interaction per primary user task. Fall back to non-browser testing only when
> no UI surface exists or the Playwright MCP server is unavailable -- and report
> the missing prerequisite rather than silently skipping.
## When NOT to load
- Static HTTP fetches (use the agent's normal fetch tool).
- Bulk crawling, scraping behind auth, or anything outside the Frontier security profile's URL allowlist (see Anti-Patterns).
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_tf4wvybgc5z3g3l2
GET https://markdownregistry.com/api/v1/resolve?ref=jnpiyush/agentx/browser-automation
GET https://markdownregistry.com/api/v1/blob/400e51940935a85a01e34e7d33b27451c9d41a46ae5f1a1257e6428a4567d835
Your agent 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.
jnpiyush/agentx · .github/skills/ai-systems/agent-observability/SKILL.md · Instrument LLM agents with tracing, metrics, and evaluation telemetry. Use when adding OpenTelemetry GenAI semantic…
jnpiyush/agentx · .github/skills/ai-systems/ai-agent-development/SKILL.md · Build production-ready AI agents with Microsoft Foundry and Agent Framework. Use when creating AI agents, selecting LLM…
jnpiyush/agentx · .github/skills/ai-systems/ai-evaluation/SKILL.md · Use when evaluating AI quality, safety, completeness and cost with held-out tasks, executable graders, calibrated…
jnpiyush/agentx · .github/skills/ai-systems/ai-safety-and-red-teaming/SKILL.md · Defend LLM systems against prompt injection, jailbreaks, data exfiltration, and unsafe output. Covers input/output…
different-ai/openwork · .opencode/skills/browser-automation/SKILL.md · Local OpenWork Electron browser automation with CDP. Use when driving a local Electron dev app, browser_list…
borghei/claude-skills · engineering/browser-automation/SKILL.md · This skill should be used when the user asks to "build web automation scripts", "check browser automation for…
coco-research/coco · skills/browser-automation/SKILL.md · Use when the agent must open a URL, fill a form, click through a flow, screenshot a page, or extract data from a live…
