Lightweight Chrome automation toolkit with shared configuration, JSON-first output, and six focused scripts for starting, navigating, inspecting, capturing, evaluating, and cleaning up browser sessions.
Control an existing Chrome/Chromium instance via DevTools protocol. Use when you need to navigate pages, capture screenshots, evaluate JavaScript, inspect elements, or manage cookies in a live browser session.
/plugin marketplace add Whamp/whamp-claude-tools/plugin install whamp-browser-tools-browser-tools-plugin@Whamp/whamp-claude-toolsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
package.jsonreferences/01-getting-started.mdreferences/02-commands.mdreferences/03-troubleshooting.mdreferences/04-security.mdscripts/close.jsscripts/config.jsscripts/cookies.jsscripts/element.jsscripts/evaluate.jsscripts/navigate.jsscripts/screenshot.jsscripts/start.jsUse these scripts to control an existing Chrome/Chromium instance via the DevTools protocol. All commands share the flags --json, --quiet, --port=<number> (default 9222), --host=<host>, --ws=<ws-endpoint>, and --timeout=<ms>. When --json is omitted, machine-readable results are still emitted to STDOUT; human-readable logs go to STDERR.
| Script | Purpose | Key Flags | JSON Output Snapshot |
|---|---|---|---|
scripts/start.js | Launch Chrome with remote debugging and optional profile sync. | --profile[=path], --chrome-path=<path>, --user-data-dir=<path> | { ok, port, userDataDir, chromePath, profile } |
scripts/navigate.js | Open a URL in the active tab or a new one. | <url>, --new, `--wait=domcontentloaded | networkidle0 |
scripts/screenshot.js | Capture full page or element screenshots. | --element=<selector>, `--format=png | jpeg, --quality=<1-100>, --out=<path>` |
scripts/element.js | Resolve elements by selector/text or interactively pick them. | <selector>, --text=<string>, --click, --scroll | { ok, selector, tag, id, classes, text, visible, rect } |
scripts/evaluate.js | Execute JavaScript in the page context. | <expression>, --file=<path> | { ok, result } (with structured clone) |
scripts/cookies.js | Export, import, or clear cookies via CDP. | --export[=file], --import=<file>, --clear, --domain=<filter> | Export payload or `{ ok, imported |
scripts/close.js | Gracefully or forcefully stop Chrome. | --force | { ok, port, graceful, forced, closedTabs } |
node scripts/start.js --profile → reuse default Chrome profile; or specify --chrome-path on Linux/Windows.node scripts/navigate.js https://example.com && node scripts/evaluate.js 'document.title'.--json to produce structured payloads for toolchains.element.js supports three modes:
element.js '.selector' – direct CSS lookup.element.js --text "Buy now" – XPath text match.element.js – interactive picker; click on the desired element in Chrome within 60 s. The command captures selector metadata and emits it as JSON.node scripts/cookies.js --export cookies.json.--domain example.com (applies to export and clear).node scripts/cookies.js --import cookies.json --json (reloads the current page).node scripts/close.js for graceful closure; add --force when the DevTools endpoint is unresponsive.This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.