How do I install the Macos Harness skill?

Run npx skillmds@latest add aska-digital/macos-harness in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Macos Harness safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Macos Harness?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Macos Harness free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Macos Harness?

aska-digital (@aska-digital) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Macos Harness by aska-digital — Agent Skill

Name: Macos Harness
Rating: 4.2 (5 reviews)
Author: aska-digital

File contents

macos-harness / browser-harness

Installed via uv tool install --python 3.12 (macos-harness 0.1.x + browser-harness). Upgrade protocol: re-audit both upstream repos against the new commit before distributing. Treat upgrades as reviewed changes — a bump introduces new code into every trust boundary at once.

Split-of-duties convention

cua-driver (computer_use) owns see/click/type/key — default for all desktop interaction.
macos-harness ONLY for: (a) real-Chrome CDP via browser-harness browser.*, (b) persistent-process Python composition when one-action-per-call can't do it, (c) bottom rung of the verify→escalate ladder after cua-driver returns unverifiable/suspected_noop.

Hard gates

Never call browser.connect() without an explicit user go — it auto-approves AX prompts, may LAUNCH Chrome if closed, and opens chrome://inspect tabs. Controlled tab's title gets a 🐴 prefix.
Never trigger cloud profile-sync (api.browser-use.com) — copies local cookies to their cloud. Auth-gated only.
Telemetry is OFF — enforcement layer is the 0600 config files (~/.config/browser-harness/telemetry.json and ~/Library/Application Support/macos-harness/telemetry.json, both "disabled": true, verified on a non-interactive shell). The BH_TELEMETRY=0 / MACOS_HARNESS_TELEMETRY=0 vars in ~~/.zshrc are belt-and-suspenders only: zshrc doesn't load for non-interactive agent/cron shells. browser-harness ignores DO_NOT_TRACK and its cli_event telemetry ships full task scripts (~~20KB) bypassing redaction — never re-enable.
No kill-switch env var exists for AX auto-approve; the gate is procedural only.

Six primitives

mac.see(app), mac.key(combo, app=...), mac.type(text, app=...), mac.click(x, y, app=...), mac.ax.at(x, y, app=...), mac.script('AppleScript'); plus browser.* (CDP), Path, subprocess in the same process. Background capture — never raises apps or moves the real cursor.

macos-harness <<'PY'
frame = mac.see("Spotify")
mac.key("cmd+k", app="Spotify")
PY

State

Permissions verified: accessibility ✓ screen_recording ✓ post_events ✓. Verified live: apps listing + background capture of Finder. Restart discipline: harness process is stateful — restart before trusting stale screen state.

---name: macos-harnessdescription: Use when a task needs driving the user's real logged-in Chrome (CDP) or composing multi-step logic in one persistent Python process — the escape hatch when cua-driver hits unverifiable/suspected_noop.---# macos-harness / browser-harnessInstalled via `uv tool install --python 3.12` (macos-harness 0.1.x + browser-harness). **Upgrade protocol: re-audit both upstream repos against the new commit before distributing.** Treat upgrades as reviewed changes — a bump introduces new code into every trust boundary at once.## Split-of-duties convention- cua-driver (`computer_use`) owns `see`/`click`/`type`/`key` — default for all desktop interaction.- macos-harness ONLY for: (a) real-Chrome CDP via browser-harness `browser.*`, (b) persistent-process Python composition when one-action-per-call can't do it, (c) bottom rung of the verify→escalate ladder after cua-driver returns `unverifiable`/`suspected_noop`.## Hard gates- **Never call `browser.connect()` without an explicit user go** — it auto-approves AX prompts, may LAUNCH Chrome if closed, and opens chrome://inspect tabs. Controlled tab's title gets a 🐴 prefix.- Never trigger cloud profile-sync (api.browser-use.com) — copies local cookies to their cloud. Auth-gated only.- Telemetry is OFF — enforcement layer is the 0600 config files (`~/.config/browser-harness/telemetry.json` and `~/Library/Application Support/macos-harness/telemetry.json`, both `"disabled": true`, verified on a non-interactive shell). The `BH_TELEMETRY=0` / `MACOS_HARNESS_TELEMETRY=0` vars in ~/.zshrc are belt-and-suspenders only: zshrc doesn't load for non-interactive agent/cron shells. browser-harness ignores DO_NOT_TRACK and its cli_event telemetry ships full task scripts (~20KB) bypassing redaction — never re-enable.- No kill-switch env var exists for AX auto-approve; the gate is procedural only.## Six primitives`mac.see(app)`, `mac.key(combo, app=...)`, `mac.type(text, app=...)`, `mac.click(x, y, app=...)`, `mac.ax.at(x, y, app=...)`, `mac.script('AppleScript')`; plus `browser.*` (CDP), `Path`, `subprocess` in the same process. Background capture — never raises apps or moves the real cursor.```bashmacos-harness <<'PY'frame = mac.see("Spotify")mac.key("cmd+k", app="Spotify")PY```## StatePermissions verified: accessibility ✓ screen_recording ✓ post_events ✓. Verified live: `apps` listing + background capture of Finder. Restart discipline: harness process is stateful — restart before trusting stale screen state.

Frequently asked questions

Macos Harness