Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/ruchit-p/macwright/agents-mdgit clone --depth 1 https://github.com/ruchit-p/macwrightWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.01232 | $0.01232 |
| Opus 5 | $0.00616 | $0.00616 |
| Sonnet 5 | $0.00246 | $0.00246 |
| Haiku 4.5 | $0.00123 | $0.00123 |
Grade A, and why
macwright AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MacWright Agent Guide
MacWright is an MCP server for native macOS desktop control. Use this file as the first-stop guide for any coding agent or LLM working in this repo.
Project Basics
- Runtime: Node.js >= 18, TypeScript.
- Server entry:
src/index.ts. - Tool implementations:
src/tools/**. - Shared helpers:
src/utils/**. - Built server:
dist/index.js. - Build:
npm run build. - Portable schema test:
npm test. - Native macOS smoke test:
npm run test:macos-smoke. - Setup/doctor:
./setup.shand./setup.sh --doctor.
Setup and Permissions
Run the setup/doctor script instead of guessing what is broken:
./setup.sh # install deps, build, run checks
./setup.sh --doctor # checks only; no install/build
./setup.sh --open-settings # open relevant macOS Privacy panes
./setup.sh --install-omniparser # also run omniparser/setup.sh
./setup.sh --start-omniparser # start OmniParser after checks
macOS TCC permissions cannot be silently bypassed by normal scripts. The setup script can preflight, open the right panes, and verify readiness, but the user must manually approve permissions and then restart the controlling app.
Required/important permissions:
| Permission | Needed for |
|---|---|
| Accessibility | mouse, keyboard, scroll, AX read/click, focus/resize window via System Events |
| Screen Recording | screenshots, screen_parse, visual verification, wait_for_change |
| Input Monitoring / Automation prompts | may be requested by macOS depending on controlling app, keyboard events, Apple Events, or target app |
| Safari JavaScript from Apple Events | Safari JS tools; enable Safari Develop menu + “Allow JavaScript from Apple Events” |
Native Control Strategy
Do not assume one API works for every app. Use a layered strategy:
- Accessibility API for semantic native UI control when the app exposes a useful AX tree.
- Screen-first visual fallback when AX is weak: screenshot or
screen_parse-> click/type/shortcut -> visual verification. - Raw mouse/keyboard/clipboard/hotkeys as the lowest-level universal layer.
- Always verify the result with
verifyChange,screenshot,screenshotAfterClick,wait_for_change,read_ui, or another parse.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday First seen · 121 lines · 1,232 tokens per session scan A 948bfc3c6da9
macwright AGENTS.md is an instructions file published in the GitHub repository ruchit-p/macwright (0 stars, last pushed 20d ago), licensed MIT. It adds 1,232 tokens to every session, about $0.0062 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
barkeep AGENTS.md
Instructions for iannuttall/barkeep, covering agent notes, product rules, repo map, commands and app structure.
Loupe CLAUDE.md
Instructions for smughead/Loupe, covering claude.md, build commands, build the app (from project root), run all tests (unit + ui) and run only spm package unit tests.
blurt AGENTS.md
Instructions for AssemblyAI/blurt, covering agents.md, start here, the two layers, repository map and verifying your work.
blurt CLAUDE.md
Instructions for AssemblyAI/blurt, covering claude.md, hooks (.claude/settings.json), skills (.claude/skills/), subagents (.claude/agents/) and permissions.
OpenAra AGENTS.md
Instructions for Aradotso/OpenAra, covering openara agent guide, read first, working rules and where things live.
barkeep CLAUDE.md
Instructions for iannuttall/barkeep, a project described as: Manage hidden macOS menu bar items from one place.