HiyokoSauna37

Kb Browser — Testing skill for Claude Code

Testing community

A browser you drive entirely from the CLI — Playwright + Chromium, DevTools in the terminal, restart-free proxy profiles, and an MCP server for AI agents (Claude Code).

How to install Kb Browser

This entry records only its repository, not the path inside it, so there is no exact command to give. Open HiyokoSauna37/kb-browser and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Kb Browser does

A browser you drive entirely from the CLI — Playwright + Chromium, DevTools in the terminal, restart-free proxy profiles, and an MCP server for AI agents (Claude Code).

Alternatives in Testing

  • Playwright — claude-plugins-official Browser automation, E2E testing, screenshots 29.4k ★
  • Playwright — Automate real browser interactions for navigation, forms, and scraping 14.6k ★
  • Playwright Automation — git clone Browser automation skill for end-to-end testing and web interaction 2.3k ★

README

kb — CLI Browser

A browser you operate entirely from the command line. Built on Playwright + Chromium (CDP).

MIT License "Node= 18"> Playwright + Chromium MCP · 34 tools

日本語版は [README.ja.md](README.ja.md) を参照してください。

Everything a GUI browser gives you — page rendering, cookie management, DevTools operations (Network / Console / Elements) — is available as `kb` commands. FoxyProxy-style proxy profiles are built in, with **restart-free switching** and per-host routing rules. Designed to be driven by AI agents (Claude Code, etc.) via Bash or MCP, while the window is a real Chrome you can use by hand at any time.

**Two workflows it's built for:**

  • Drive it from an AI agent — Claude Code and other agents operate kb over MCP (34 tools) or Bash (every command supports JSON action results). The accessibility-snapshot + --ref loop is tuned for reliable, low-token automation, and the resident daemon returns each step in tens of milliseconds.
  • Security research & bug-bounty recon (authorized testing only) — session-shared HTTP, live network inspection/mocking, raw eval on authenticated SPAs, proxy chaining into Burp/Caido, two-account IDOR via profiles, and masked, shareable evidence bundles. See Security research & bug-bounty recon.

Features

  • Daemon architecture — the browser stays resident; every CLI command returns in tens of milliseconds
  • Uses installed Chrome/Edge — prefers a real browser with DRM support and falls back to bundled Chromium