peek AGENTS.md

A macOS command-line tool and MCP server for inspecting and controlling native application windows. It can read an app’s accessibility tree, find interface elements, interact with them, control menus, take screenshots, and manage app launch and exit.

In plain words
What is it for?
Use it when developing Peek itself: build it with Swift, run its commands, understand its folder structure, and work with its command-line and MCP interfaces.
Why use it?
It gives coding agents a way to inspect and operate desktop apps instead of working only with files or web pages. The instructions also explain how to build and run the Swift project and manage releases.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/alexmx/peek/agents-md
Clone the repo
git clone --depth 1 https://github.com/alexmx/peek

Made for: Codex, OpenCode.

Per session 2,078 This file is loaded in full into every session.
When invoked 2,078 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.02078 $0.02078
Opus 5 $0.01039 $0.01039
Sonnet 5 $0.00416 $0.00416
Haiku 4.5 $0.00208 $0.00208

Measured 2d ago against content hash f2b128c4e8f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

peek 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 2d ago.

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.

AGENTS.md · 118 lines

How it starts

The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Peek

What is Peek?

Peek is a macOS CLI tool and MCP server for inspecting and automating native application windows. It provides accessibility tree inspection, element search, UI interaction (click, type, actions), menu bar control, screenshots, and app lifecycle control (launch/quit).

Project Structure

peek/
├── Package.swift                    # SPM manifest (macOS 15+, Swift 6.2)
├── Sources/Peek/
│   ├── Peek.swift                   # @main entry point, registers all subcommands
│   ├── Commands/                    # One file per CLI command
│   ├── Managers/                    # Core business logic (stateless enum singletons)
│   ├── Models/                      # Data types (AXNode, WindowInfo, PeekError, etc.)
│   ├── MCP/
│   │   └── PeekTools.swift          # MCP tool definitions, mirrors CLI 1:1
│   └── Utilities/                   # AX helpers, key mapping, output formatting

Build & Run

swift build
swift run peek <command> [options]

Requirements: macOS 15+, Swift 6.2, Xcode toolchain.

Dependencies:

  • swift-argument-parser — CLI argument parsing
  • swift-cli-mcp — MCP server framework

Version Management & Releases

Version Source: .peek-version file in repository root

  • Single source of truth for version number (e.g., 1.0.0 or dev)
  • Sources/Peek/Version.swift defines peekVersion constant (defaults to "dev" for local builds)
  • GitHub Actions reads .peek-version, generates Version.swift with actual version, then builds release binary
  • CLI exposes version via peek --version

Release Process:

  1. Update .peek-version with new version (e.g., 1.0.0)
  2. Commit and push to main

That's it — pushing a change to .peek-version automatically runs the "Release" workflow (.github/workflows/release.yml; also runnable manually via workflow_dispatch), which:

  • Creates the git tag and builds the universal binary (skips if the tag already exists)
  • Publishes the GitHub release
  • Updates the Homebrew formula in the homebrew-tools repository with the new version and SHA256

Read the full file on GitHub · 118 lines

Changes

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.

  1. 2d ago First seen · 118 lines · 2,078 tokens per session scan A f2b128c4e8f1

Subscribe to this mod's changes

peek AGENTS.md is an instructions file published in the GitHub repository alexmx/peek (5 stars, last pushed 1mo ago), licensed MIT. It adds 2,078 tokens to every session, about $0.0104 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.