What is chrome-devtools-mcp-skill?

A read-only helper for Blocknative, a service that provides information about blockchain transaction fees. It focuses on gas prices, which are the fees paid to process blockchain transactions, including newer data such as blob fees.

Discover supported blockchain networks, estimate gas-price confidence, predict base and blob fees, and analyze the distribution of pending gas prices.

It avoids manually forming requests for fee estimates and pending-transaction analysis. It does not submit transactions or provide live mempool event streaming.

chrome-devtools-mcp-skill — Skill for Codex by holon-run: A read-only helper for Blocknative, a service that provides…

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/holon-run/uxc/chrome-devtools-mcp-skill

Any agent

npx skills add holon-run/uxc --skill chrome-devtools-mcp-skill

Clone the repo

git clone --depth 1 https://github.com/holon-run/uxc

Made for: Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/holon-run/uxc/chrome-devtools-mcp-skill.svg)](https://agentmods.dev/skills/holon-run/uxc/chrome-devtools-mcp-skill)

Your own site

<a href="https://agentmods.dev/skills/holon-run/uxc/chrome-devtools-mcp-skill"><img src="https://agentmods.dev/badge/skills/holon-run/uxc/chrome-devtools-mcp-skill.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,121 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.1	$0.00056	$0.01121
Opus 5	$0.00028	$0.00561
Sonnet 5	$0.00011	$0.00224
Haiku 4.5	$0.00006	$0.00112

Measured 6d ago against content hash b6c9d0d66144, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

chrome-devtools-mcp-skill 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 6d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate.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.

skills/chrome-devtools-mcp-skill/SKILL.md · 89 lines

How it starts

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

Chrome DevTools MCP Skill

Use this skill to run Chrome DevTools MCP operations through uxc using a fixed stdio endpoint.

Reuse the uxc skill for generic MCP discovery, daemon reuse, JSON envelope parsing, and error handling.

Prerequisites

uxc is installed and available in PATH.
npx is available in PATH (Node.js installed).
Chrome 144+ is running locally with remote debugging enabled from chrome://inspect/#remote-debugging if you use the default live-browser flow.
Network access is available for first-time chrome-devtools-mcp package fetch.

Core Workflow (Chrome DevTools MCP-Specific)

Endpoint candidate inputs before finalizing:

Raw package form from official docs:
- npx chrome-devtools-mcp@latest
Reliable non-interactive form:
- npx -y chrome-devtools-mcp@latest
Default live-browser endpoint for this skill:
- npx -y chrome-devtools-mcp@latest --autoConnect --no-usage-statistics
Explicit browser-url endpoint:
- npx -y chrome-devtools-mcp@latest --browserUrl http://127.0.0.1:9222 --no-usage-statistics
Fallback isolated endpoint:
- npx -y chrome-devtools-mcp@latest --headless --isolated --no-usage-statistics
Running local Chrome auto-connect mode:
- npx -y chrome-devtools-mcp@latest --autoConnect --no-usage-statistics

Verify protocol/path from official source and probe:
- Official source:
  - https://github.com/ChromeDevTools/chrome-devtools-mcp
- probe candidate endpoints with:
  - uxc "npx -y chrome-devtools-mcp@latest --autoConnect --no-usage-statistics" -h
- Confirm protocol is MCP stdio (protocol == "mcp" in envelope).
Detect auth requirement explicitly:
- Run host help or a minimal read call and inspect envelope.
- Default local stdio flow requires no OAuth/API key.
- Existing Chrome attachment requires remote debugging to be enabled separately, but not API auth.
Use a fixed link command by default:
- command -v chrome-devtools-mcp-cli
- If missing, create it:
  - uxc link chrome-devtools-mcp-cli "npx -y chrome-devtools-mcp@latest --autoConnect --no-usage-statistics"
- Optional explicit browser-url link:
  - command -v chrome-devtools-mcp-port
  - uxc link chrome-devtools-mcp-port "npx -y chrome-devtools-mcp@latest --browserUrl http://127.0.0.1:9222 --no-usage-statistics"
- Optional isolated fallback link:
  - command -v chrome-devtools-mcp-isolated
  - uxc link chrome-devtools-mcp-isolated "npx -y chrome-devtools-mcp@latest --headless --isolated --no-usage-statistics"
- chrome-devtools-mcp-cli -h
Inspect operation schema before execution:
- chrome-devtools-mcp-cli new_page -h
- chrome-devtools-mcp-cli take_snapshot -h
- chrome-devtools-mcp-cli list_network_requests -h
- chrome-devtools-mcp-cli lighthouse_audit -h
Prefer read-first interaction:
- Start with new_page, list_pages, take_snapshot, list_network_requests, or list_console_messages.
Confirm before mutating page state:
- click
- fill
- fill_form
- press_key
- upload_file
- evaluate_script
- handle_dialog

Read the full file on GitHub · 89 lines

Files

What ships with it

3 files 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.

6d ago First seen · 89 lines · 56 tokens per session scan A b6c9d0d66144

Subscribe to this mod's changes

chrome-devtools-mcp-skill is a skill published in the GitHub repository holon-run/uxc (113 stars, last pushed 28d ago), licensed MIT. It adds 56 tokens to every session and 1,121 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-30.

Browser automation agent-tools ai-agents api cli developer-tools graphql

linear

Linear project management — issues, cycles, and projects via GraphQL API.

furkangonel/cowrangler · 17 tokens

create-tutorial

Scaffold a new Membrane API Gateway tutorial in the api-gateway repo — the numbered self-teaching YAML under distribution/tutorials/ /, its support files and README links, and the matching auto-discovered integration test. Use whenever the user asks to create, add, write, or scaffold a tutorial (or a tutorial step)…

membrane/api-gateway · 97 tokens

optimize-interceptor-docs

Rewrite the reference documentation of a Membrane config element so the page generated at membrane-api.io comes out clean, exact, and reference-style. Use whenever the user wants to write, improve, optimize, polish, or review the docs / Javadoc / @description / @yaml example of an interceptor, plugin, or any…

membrane/api-gateway · 173 tokens

membrane-config

Generate a Membrane API Gateway configuration example or snippet — an apis.yaml (default) or, when explicitly asked, a legacy proxies.xml. Use this whenever the user wants a config, example, or snippet for Membrane: routing a port to a backend, a flow with plugins (setHeader, rateLimiter, basicAuthentication, openapi…

membrane/api-gateway · 167 tokens

release-notes

Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…

membrane/api-gateway · 124 tokens

review-branch

Review the current git branch against master — code quality, refactoring opportunities, regressions, correctness, and test coverage — and print a severity-grouped markdown report. Use whenever the user asks to review the branch, review their changes against master, do a pre-PR / pre-merge review, or asks "is this…

membrane/api-gateway · 125 tokens