Download for MacApple silicon, macOS 14+
Skill

Interceptor

@danielmiessler Updated 2026-10-28

Real Chrome plus macOS Computer Use from inside the browser, real sessions; mandatory for visual deploy verification. USE WHEN verify deploy, confirm UI, screenshot verification, debug web, visual check, animation bug, console errors, JS errors, network traffic, HAR export, blank-page debug, what is happening on the page, authenticated page, reproduce bug, drive native app. NOT FOR pixel-only GUI work (ComputerUse), crawling (BrightData), scraping.

aiai-harnessaugmentationcodinghumansintent-engineeringlifeospersonal-ai

Install

With your agent

Install OMGSkills skill "danielmiessler/LifeOS:Interceptor" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/danielmiessler/LifeOS /tmp/LifeOS && ln -s /tmp/LifeOS/LifeOS/install/skills/Interceptor ~/.claude/skills/Interceptor

From README

Interceptor Contents: Ideal State · Intent Routing · Data & Config · Gotchas · Examples Drives the real Chrome test profile and native macOS apps through the interceptor CLI and guarded wrappers. Ideal State Every browser action ran in the pinned isolated test context, only after that run's preflight gate exited 0; the operator's Default profile, windows and focus are untouched, and a gate failure ends the run instead of falling back. Browser work the operator would otherwise do by hand (open, click, fill, log in) was driven by the agent, up to the single step that needs a secret it does not hold or an OAuth or consent screen, where the operator sees the client, scopes and account and approves. Every "verified", "works" or "fixed" claim cites evidence from the real page or app: a structured read, console and network state, and a Tools/Capture.sh screenshot that was read; motion and lifecycle claims come from Tools/VerifyViewport.ts or a ScrubFlow gallery.