browser-data-capture

Plugin browser-data-capture in danielrosehill/Claude-Browser-Data-Capture-Plugin. Commands read from the repo's manifest — 22 days ago.

Skills (8)

• analyze-har

  Analyze a HAR file (HTTP Archive — exported from Chrome/Firefox DevTools → Network tab → Save all as HAR with content) and produce a normalized inventory of the endpoints it captured, with inferred request/response schemas, auth scheme detection, and a human-readable summary. The zero-install captur

• capture-via-proxy

  Capture network traffic via a local mitmproxy instance and emit a normalized capture file the rest of the plugin can analyze. Use when the user wants to capture traffic from a desktop app, mobile app on the same network, or a browser without using DevTools — anywhere a HAR export isn't practical. Th

• create-domain-map

  Produce or update a versioned "domain map" document for a single host — a curated, human-readable summary of what's been learned about a target across one or many capture runs. Aggregates endpoints, auth scheme, pagination style, rate-limit signals, ToS notes, and integration notes the user has adde

• disclose-finding

  Help the user act as a good-faith reporter when a capture run incidentally surfaces something that looks like an unauthenticated endpoint exposing data that probably shouldn't be public, a leaked token in a response, or another security-relevant finding. Drafts a courteous, vendor-friendly disclosur

• generate-openapi

  Generate a draft OpenAPI 3.1 spec from an endpoints inventory produced by analyze-har, capture-via-proxy, or observe-tab. Reads endpoints.json + inferred schemas and emits openapi.yaml plus openapi.json. Use when the user wants to build a stable client against a captured surface — "make an OpenAPI s

• init-private-repo

  Set up a private GitHub repository for version-controlling the user's domain maps and capture history. Creates the repo via gh, clones locally to a user-chosen path, scaffolds the standard layout (maps/, captures/, README, .gitignore), and registers the local path in the plugin's config so create-do

• observe-tab

  Optional convenience path — observe a live browser tab via the claude-in-chrome MCP server (read_network_requests) and build an endpoint inventory as the user interacts with the page. Useful when the user is already driving a tab and doesn't want to set up a proxy or export a HAR. Requires the claud

• setup

  First-run setup for Browser-Data-Capture — provisions the user data folder under the standard $CLAUDE_USER_DATA pattern, optionally registers a path to the user's private maps repo for version-controlled storage, and verifies dependencies (mitmproxy, genson, pyyaml, optional openapi-spec-validator).

Similar plugins