By jongwony
Attach to running CDP instance: tab management, screenshots, interaction, network/console monitoring
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimRoute upstream epistemic deficits and evaluate execution-time risks — /attend (προσοχή: attention)
Validate structural mapping between domains — /ground (ἀναλογία: a proportion)
Define epistemic boundaries per decision — /bound (ὁρισμός: a bounding)
Detect application-context mismatch after execution — /contextualize (ἐφαρμογή: an application)
Surface potential gaps at decision points — /gap (συνείδησις: knowing-together)
npx claudepluginhub jongwony/cc-plugin --plugin cdp-attachBETA: VERY LIGHTLY TESTED - Direct Chrome DevTools Protocol access via 'browsing' skill. Skill mode (17 CLI commands) + MCP mode (single use_browser tool). Zero dependencies, auto-starts Chrome.
Target-first local Chrome/Chromium browser control with signed-in profiles, labeled tabs, and guarded actions
Chrome DevTools Protocol (CDP) browser automation, web scraping, and crawling with React compatibility
Direct browser control via CDP. Drives the user's real Chrome (or a Browser Use cloud browser) with coordinate clicks, screenshots, and Python helpers — no selector hunting. Requires the one-time `browser-harness` CLI install (see the skill's references/install.md).
Generic app state capture — screenshots, HAR, console, logs via CDP
Control a local Chrome browser from Claude Code — navigate, click, type, screenshot, OCR, and more. Powered by Puppeteer.