What is browser-control?

A browser-automation skill for controlling logged-in web applications through Chrome DevTools.

Use it to navigate sites, fill forms, download reports, and verify results in applications such as PowerSchool.

It removes repetitive manual work in websites that require an existing login session.

browser-control — Skill by psd401

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.

agentmods

npx agentmods add skills/psd401/psd-claude-plugins/browser-control

Any agent

npx skills add psd401/psd-claude-plugins --skill browser-control

Clone the repo

git clone --depth 1 https://github.com/psd401/psd-claude-plugins

Made for: Claude Code, Codex.

Or install psd-productivity, the plugin that ships this one along with the rest of its 37 skills, 1 command, 8 agents.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,369 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00058	$0.01369
Opus 5	$0.00029	$0.00685
Sonnet 5	$0.00012	$0.00274
Haiku 4.5	$0.00006	$0.00137

Measured 2d ago against content hash 65a42805c122, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

browser-control 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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/launch-chrome.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/psd-productivity/skills/browser-control/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Browser Control — Chrome DevTools MCP

You automate browser interactions for authenticated web applications using Chrome DevTools Protocol. This connects to a running Brave Browser Nightly instance with a persistent debug profile that preserves login sessions.

Setup — Launch Browser

Before any browser interaction, ensure the debug browser is running:

bash plugins/psd-productivity/skills/browser-control/scripts/launch-chrome.sh

If the script reports already_running, the browser is ready. If started, wait a moment for it to initialize.

First-time setup: After launching, manually log into any sites you need (PowerSchool, Google, etc.). The persistent profile at ~/.psd-browser-automation saves cookies and sessions across restarts.

Core Workflow

Check browser status — run launch script with --status
Launch if needed — run launch script (no args for visible window)
Navigate — use navigate_page to go to URLs
Interact — use click, fill, fill_form, type_text, press_key
Verify — use take_screenshot or take_snapshot to confirm state
Wait — use wait_for when pages are loading or processing

Tool Reference

Navigation & Pages

navigate_page — go to a URL
list_pages — list open tabs
select_page — switch to a tab
new_page — open new tab
close_page — close a tab
resize_page — change viewport size
handle_dialog — accept/dismiss browser dialogs
get_tab_id — get current tab identifier

Input

click — click an element by CSS selector or text
click_at — click at x,y coordinates
hover — hover over an element
fill — fill an input field (clears first)
type_text — type text character by character
fill_form — fill multiple form fields at once
press_key — press keyboard keys (Enter, Tab, Escape, etc.)
upload_file — upload a file to a file input
drag — drag from one element to another

Observation

take_screenshot — capture visible page as image
take_snapshot — get accessibility tree (structured page content)
wait_for — wait for an element, text, or network idle
evaluate_script — run JavaScript in the page context

Read the full file on GitHub · 126 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/launch-chrome.sh 1.7 KB runs code

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.

2d ago First seen · 126 lines · 58 tokens per session scan A 65a42805c122

Subscribe to this mod's changes

browser-control is a skill published in the GitHub repository psd401/psd-claude-plugins (2 stars, last pushed 10d ago), licensed MIT. It adds 58 tokens to every session and 1,369 once invoked, about $0.0003 per session on Opus 5. 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

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include…

vercel-labs/agent-browser · 112 tokens

use-agent-browser-for-airi

Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…

moeru-ai/airi · 87 tokens

opencli-sitemap-author

Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.

jackwener/OpenCLI · 67 tokens

playwright

Use when the task requires automating a real browser from the terminal (navigation, form filling, snapshots, screenshots, data extraction, UI-flow debugging) via playwright-cli or the bundled wrapper script.

XiaomiMiMo/MiMo-Code · 45 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

peekaboo

Capture and automate macOS UI with the Peekaboo CLI.

the-open-agent/openagent · 17 tokens