Skip to content
SkillScript-led2,617 tokens in use

Browser CDP

Start a debug copy of your Chrome with its saved logins and drive it through agent-browser: open pages, run JavaScript, click and read page text.

8,793 stars on the repository MIT Licensezenstory-ai/oh-story-claudecode · skills/browser-cdp
npx skills add zenstory-ai/oh-story-claudecode -y -g
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Browser CDP costs

99tokens idle
2,617tokens in use

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/setup-cdp-chrome.js.

Touches

shelldetectednetworkdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure16/25
  • Examples12/15
  • Output10/15
  • Size15/15
  • Resources15/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 27
  • Reaches the network−10

    does this on the machine, and the frontmatter does not say so

    scripts/setup-cdp-chrome.js, line 219

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity100
  • Maintenance100
  • Community60
  • Maturity28
  • Momentum40

Browser CDP connects an agent to Google Chrome through the Chrome DevTools Protocol so it can work with sites you are already signed in to. A bundled Node script checks whether a debug Chrome is already listening, and if not, copies your Chrome profile into a separate debug profile and launches Chrome on a debugging port. The agent then uses the agent-browser command line tool to open pages, wait, evaluate JavaScript, take snapshots, click, type and extract text or tokens.

In the Oh Story writing toolkit it supplies the logged-in browser session that the ranking scan skills use to read web novel charts. The skill asks for your consent before it closes any running Chrome.

What You Get

  • A debug Chrome on port 9222 (or another port) that carries your copied login state
  • agent-browser commands to open pages, wait, evaluate JavaScript, take snapshots, click and type
  • A consent flow with dry run, exit codes and a refusal to kill Chrome without agreement
  • Timeout wrappers for slow page loads and batch scraping, plus a troubleshooting table

Common Use Cases

  • Reading pages that need a login without handling passwords
  • Scraping ranking pages for the Oh Story scan skills
  • Extracting a page’s text or an auth token from local storage
  • Automating clicks and typing in a signed-in browser

What Makes It Unique

It reuses the login state of your own Chrome profile, so the agent never asks for credentials. Its setup script is built around safety checks: a detect-only mode, an explicit consent step before closing Chrome, a hard stop when the debug port is held by another process, and identity checks that the port answers from the instance it launched.

Under The Hood

The skill has one bundled script, a Node program that detects Chrome, may stop running Chrome processes (only with your consent), copies your Chrome profile, including cookies and saved login files, into a separate debug profile folder in your home directory, and starts Chrome with remote debugging on a local port. The instructions then tell the agent to run the agent-browser command line tool, which you install with npm, to open web pages, evaluate JavaScript in them and read page text or tokens from local storage. It also names kill commands for cleanup of the debug instance only. The copied profile keeps your logins on disk until you delete it, and any agent able to reach the debug port can act as you in that browser.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers