A browser-automation plugin built around Playwright, a tool for controlling a web browser with code. It keeps page state between actions and can navigate sites, enter data, capture screenshots, extract information, and test web apps.

For navigating websites, filling forms, taking screenshots, collecting web data, and automating browser-based tests.

It removes repetitive manual browser work and lets you inspect or test a site through realistic user actions.

dev-browser — Plugin by patelr3

Install

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.

Claude Code

/plugin marketplace add patelr3/agents

agentmods

npx agentmods add plugins/patelr3/agents/dev-browser

Clone the repo

git clone --depth 1 https://github.com/patelr3/agents

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

dev-browser 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 yesterday.

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.

plugins/dev-browser/.claude-plugin/plugin.json · 26 lines

What it actually says

{
  "name": "dev-browser",
  "version": "1.0.0",
  "description": "Browser automation with persistent page state via Playwright. Navigate websites, fill forms, take screenshots, extract web data, test web apps, and automate browser workflows.",
  "author": {
    "name": "patelr3",
    "url": "https://github.com/patelr3"
  },
  "homepage": "https://github.com/patelr3/agents",
  "repository": "https://github.com/patelr3/agents",
  "license": "MIT",
  "keywords": ["browser", "playwright", "automation", "screenshots", "scraping", "testing", "web"],
  "hooks": {
    "SessionStart": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "diff -q \"${CLAUDE_PLUGIN_ROOT}/package.json\" \"${CLAUDE_PLUGIN_DATA}/package.json\" >/dev/null 2>&1 || (cd \"${CLAUDE_PLUGIN_DATA}\" && cp \"${CLAUDE_PLUGIN_ROOT}/package.json\" . && cp \"${CLAUDE_PLUGIN_ROOT}/package-lock.json\" . 2>/dev/null; npm install --production) || rm -f \"${CLAUDE_PLUGIN_DATA}/package.json\""
          }
        ]
      }
    ]
  }
}

Changes

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.

yesterday First seen · 26 lines scan A a2b165c2aed1

Subscribe to this mod's changes

dev-browser is a plugin published in the GitHub repository patelr3/agents (2 stars, last pushed 4mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-31.

Browser automation Productivity Testing

dev-browser

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other plugins, from other repositories

cli

hhru

dhm

kernel-sdks

webmcpify

realbrowser