browser-debugger-cli

Name: browser-debugger-cli Review
Item: browser-debugger-cli
Rating: 3.0
Author: Aaron Matthews

Skill Development Usable

Works inClaude Code

Usable Scanned — metadata only

Enables AI agents to inspect and debug browser state programmatically without screenshots, reducing iteration cycles and enabling headless automation of comp…

Let Claude Code and other coding agents drive and debug Chrome from the shell. DOM, network, console and raw CDP as short commands, no screenshots and no MCP needed.

Automate Chrome debugging workflows without taking screenshots or screenshots
Execute DOM queries and inspect network requests directly from shell commands
Run console commands and raw Chrome DevTools Protocol actions in code agents

180 starsMIT (commercial OK)FreeQuick setup

Usable rating — This tool is functional but has notable gaps. Review the evaluation notes below before deploying.

Why it matters

Enables AI agents to inspect and debug browser state programmatically without screenshots, reducing iteration cycles and enabling headless automation of complex front-end debugging tasks.

Best for

Teams automating end-to-end testing and debugging workflows where Claude Code agents need direct browser introspection and DOM manipulation.

Works in

Claude Code Claude Cowork Claude Chat

Source

https://github.com/szymdzum/browser-debugger-cli

By szymdzum

How to Get It

Option 1: Claude Desktop App (Code Mode)Click the + button next to the prompt box → Plugins → Add plugin. Search and click Install. Skills work in Claude Code only.

Option 2: Paste into Claude CodeCopy the command below and paste it into your conversation. Claude will install it.

Command

claude plugins install szymdzum/browser-debugger-cli

Tip: Paste this into a Claude Code conversation. Verify command matches your Claude Code version.

Auto-generated from the tool's public listing — not hands-on verified. Cross-check against the source repo's README before running.

First thing to try

After installing, paste this into Claude:

Help me automate Chrome debugging workflows without taking screenshots or screenshots

CostFree

Trust Signals Auto-scanned

Stars180Contributors6Last updated2026-10-22LicenseMIT (OK for commercial use)Known CVEsNone foundSources: GitHub Advisory Database + OSV.dev · Scanned 2026-10-22 · scanner v1

Community Pulse Quiet

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Scored from trust signals (evidence-eval-v1): 175 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

Things to check

Scanned, not hands-on tested — this entry was auto-scanned from public metadata (GitHub metrics, license, security flags). No reviewer has run it, and no tool-specific limitations have been documented yet.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation Scores

Evaluation

Ease of Use

3/5

Versatility

3/5

Reliability

3/5

Security

3/5

Overall score3.00 / 5.00 UsableEvaluatedOct 2026

Scored from trust signals (evidence-eval-v1): 175 GitHub stars; contributors unknown; last commit 0d ago; license MIT.

← Back to the Claude Observatory