chrome-devtools-cli

Instructions for using the Chrome DevTools command-line tool from shell scripts or terminal commands. The tool can inspect pages, click elements, enter text, preserve browser state, and work with files.

In plain words
What is it for?
Use it to automate browser interactions from a terminal, inspect page structure, fill forms, press keys, upload files, or save results.
Why use it?
It gives command-line workflows for browser tasks, including how to identify the correct page and element before acting.

Skill for Claude CodeCodex

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/chromedevtools/chrome-devtools-mcp/chrome-devtools-cli
Any agent
npx skills add ChromeDevTools/chrome-devtools-mcp --skill chrome-devtools-cli
Clone the repo
git clone --depth 1 https://github.com/ChromeDevTools/chrome-devtools-mcp

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,733 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.

ModelPer sessionOnce invoked
Fable 5 $0.00031 $0.02733
Opus 5 $0.00015 $0.01367
Sonnet 5 $0.00006 $0.00547
Haiku 4.5 $0.00003 $0.00273

Measured yesterday against content hash 46be445e0fcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

chrome-devtools-cli 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

skills/chrome-devtools-cli/SKILL.md · 193 lines

How it starts

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

The chrome-devtools-mcp CLI lets you interact with the browser from your terminal.

Setup

Note: If this is your very first time using the CLI, see references/installation.md for setup. Installation is a one-time prerequisite and is not part of the regular AI workflow.

AI Workflow

  1. Execute: Run tools directly. If you don't know the target page's ID, run chrome-devtools list_pages to find it. The background server starts implicitly; do not run start/status/stop before each use.
  2. Inspect: Use chrome-devtools take_snapshot <pageId> to get an element <uid>.
  3. Act: Use chrome-devtools click <pageId> <uid>, chrome-devtools fill <pageId> <uid> <value>, etc. State persists across commands.

Snapshot example:

uid=1_0 RootWebArea "Example Domain" url="https://example.com/"
  uid=1_1 heading "Example Domain" level="1"

Permissions & File Access

By default, the CLI has full filesystem access (--allowUnrestrictedPaths=true), allowing file-saving parameters (--filePath, --outputDirPath) and upload_file to access files anywhere on the system. Pass --allowUnrestrictedPaths=false if you want to restrict file access to the OS temp directory.

Command Usage

chrome-devtools <tool> [arguments] [flags]
  • Required arguments are passed positionally; optional arguments use flags.
  • Use --help on any command for usage details.
  • Output defaults to plain Markdown-like text; pass --output-format=json for JSON.

Input Automation ( from snapshot)

chrome-devtools take_snapshot 1 # Take a text snapshot of the page to get UIDs for elements
chrome-devtools click 1 "id" # Clicks on the provided element
chrome-devtools click 1 "id" --dblClick true --includeSnapshot true # Double clicks and returns a snapshot
chrome-devtools drag 1 "src" "dst" # Drag an element onto another element
chrome-devtools drag 1 "src" "dst" --includeSnapshot true # Drag an element and return a snapshot
chrome-devtools fill 1 "id" "text" # Type text into an input, textarea, or select an option
chrome-devtools fill 1 "id" "text" --includeSnapshot true # Fill an element and return a snapshot
chrome-devtools handle_dialog 1 accept # Handle a browser dialog (accept/dismiss)
chrome-devtools handle_dialog 1 dismiss --promptText "hi" # Dismiss a dialog with prompt text
chrome-devtools hover 1 "id" # Hover over the provided element
chrome-devtools hover 1 "id" --includeSnapshot true # Hover over an element and return a snapshot
chrome-devtools press_key 1 "Enter" # Press a key or key combination ("Control+A", "Escape")
chrome-devtools press_key 1 "Control+A" --includeSnapshot true # Press a key and return a snapshot
chrome-devtools type_text 1 "hello" # Type text using keyboard into a focused input
chrome-devtools type_text 1 "hello" --submitKey "Enter" # Type text and press a submit key
chrome-devtools upload_file 1 "id" "file.txt" # Upload a file through a provided element
chrome-devtools upload_file 1 "id" "file.txt" --includeSnapshot true # Upload a file and return a snapshot

Read the full file on GitHub · 193 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.

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.

  1. yesterday First seen · 193 lines · 31 tokens per session scan A 46be445e0fcf

Subscribe to this mod's changes

chrome-devtools-cli is a skill published in the GitHub repository ChromeDevTools/chrome-devtools-mcp (50,208 stars, last pushed 2d ago), licensed Apache-2.0. It adds 31 tokens to every session and 2,733 once invoked, about $0.0002 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-30.

Related

Other skills, from other repositories

webview-devtools

Use webview-devtools-mcp to inspect and automate an already-instrumented WebView/page: choose this skill when the user’s target environment is configured so the page injects wdmcp’s target.js (or the user is explicitly asking to work with such a configured WebView). If the page is not yet injecting target.js, do not…

ilharp/webview-devtools-mcp · 102 tokens

brave-devtools-cli

Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Brave DevTools via CLI.

triuzzi/brave-devtools-mcp · 32 tokens

brave-devtools

Uses Brave DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).

triuzzi/brave-devtools-mcp · 56 tokens

a11y-debugging

Uses Brave DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.

triuzzi/brave-devtools-mcp · 50 tokens

troubleshooting

Uses Brave DevTools MCP and documentation to troubleshoot connection and target issues. Trigger this skill when listpages, newpage, or navigatepage fail, or when the server initialization fails.

triuzzi/brave-devtools-mcp · 40 tokens

memory-leak-debugging

Diagnoses and resolves memory leaks in JavaScript/Node.js applications. Use when a user reports high memory usage, OOM errors, or wants to capture, compare, or inspect heap snapshots with Brave DevTools MCP memory tools.

triuzzi/brave-devtools-mcp · 52 tokens