do-interceptor

Drive real Chrome and macOS apps for browser automation, visual verification, and computer use.

2|Updated May 25, 2026
One-click install
npx skills add https://github.com/edheltzel/Do-Skills --skill do-interceptor-edheltzel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: do-interceptor
Source: https://github.com/edheltzel/Do-Skills/tree/main/skills/operations/do-interceptor
Command: npx skills add https://github.com/edheltzel/Do-Skills --skill do-interceptor-edheltzel

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? CDP-based browser automation gets fingerprinted and blocked by sites, runs without your logged-in sessions, and screenshots alone cannot explain why a page broke. This Skill drives the real Chrome/Brave/Helium browser from inside via a Chrome extension, preserving authenticated sessions and passing bot detection, while exposing DOM reads, JS evaluation, console errors, and network traffic to diagnose failures like hydration mismatches and blank pages. ## Core Features & Use Cases - Six browser capability classes: visual capture (DOM-render and pixel screenshots), DOM read (accessibility tree, markdown, refs), JS eval in isolated or main world, passive network capture with HAR/pcapng export, input (click, type, keys, drag), and record/replay of user flows. - macOS Computer Use bridge: drive native apps via the accessibility tree, OS-level trusted input, backgrounded screenshots without focus changes, Apple Events dispatch, Vision OCR, and VM lifecycle management. - Enforced isolation doctrine: a mandatory preflight gate pins every command to a dedicated test Chrome profile and hard-stops rather than ever touching the operator's Default profile; raw screencapture and osascript focus-pulling are forbidden. - Use Case: After deploying a site, verify it visually by capturing a screenshot through the sanctioned Capture.sh wrapper, reading console errors via eval, and exporting the network log as HAR — all inside your signed-in test profile without disturbing your main browser window. ## Quick Start Ask the agent to verify a deployed page by running the preflight isolation gate and then capturing a screenshot of the URL through the Interceptor test profile.

Frequently Asked Questions about do-interceptor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a deployed website visually without bot detection?▼

Run the preflight isolation gate, then use Tools/Capture.sh with the target URL to capture a DOM-render screenshot through the pinned test Chrome profile. Because Interceptor operates as a browser extension rather than CDP, sites cannot fingerprint the automation and your signed-in sessions remain active.

How do I debug a blank page or hydration error in the browser?▼

Inject a console.error and window.error listener via interceptor eval --main, store events on window.__errs, then eval again to read them back. Combine this with DOM reads and net log to diagnose hydration mismatches, React errors, and silent runtime failures that screenshots cannot explain.

Does this work with authenticated pages and logged-in sessions?▼

Yes. The dedicated test Chrome profile is signed into the operator's accounts once, so sessions persist. Every command routes to that profile via --context, giving full authenticated access without ever touching the Default profile's tabs or windows.

Why did my browser command fail with a context or preflight error?▼

The preflight gate hard-stops when the pinned test context is missing, the binary is outdated, or the resolved target is the Default profile. Run Tools/EnsureTestProfile.sh to auto-launch the test profile and re-verify; exit code 7 or 8 means you must fix configuration before proceeding.

Can I control native macOS apps without changing focus?▼

Yes, with the full-mode bridge installed. Use interceptor macos commands with refs or --app flags to deliver AX presses and per-PID events to backgrounded apps, and capture windows via CGSHWCaptureWindowList without activating them. Verify with interceptor macos frontmost before and after.

What are the limitations of CDP-based browser automation compared to this approach?▼

CDP automation is detectable by bot-detection systems, runs as a separate unauthenticated browser instance, and shows a debugger banner. Interceptor avoids all three by operating through the real browser UI as an extension, though it requires Chrome running with the extension loaded.