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 skills add alexmx/peek --skill use-peekgit clone --depth 1 https://github.com/alexmx/peekWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/alexmx/peek/use-peek)<a href="https://agentmods.dev/skills/alexmx/peek/use-peek"><img src="https://agentmods.dev/badge/skills/alexmx/peek/use-peek.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00051 | $0.03072 |
| Opus 5 | $0.00026 | $0.01536 |
| Sonnet 5 | $0.00010 | $0.00614 |
| Haiku 4.5 | $0.00005 | $0.00307 |
Grade A, and why
use-peek 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
peek — macOS Window Inspector CLI
peek inspects and drives native macOS app windows via Accessibility: tree inspection, element search, UI automation, screenshots, app lifecycle, menu bar.
Requirements: macOS 15+, Accessibility permission (and Screen Recording for peek capture). Run peek doctor --prompt to grant.
Always pass --format toon for LLM workflows (30-50% fewer tokens than JSON).
Workflow
Discover → act → verify in as few calls as possible.
peek launch --name Calculator --wait-for-window # → returns pid + windowID + windowTitle
peek find --app Calculator --role Button --title 5 --limit 1
peek action --app Calculator --do Press --role Button --title 5 --verify diff
- Discover with
peek launch --wait-for-window(returns windowID) orpeek apps --app X. Skippeek appsafter launch — it's already in the result. - Inspect structure with
peek tree(unfamiliar UI) orpeek find(known labels, much cheaper —--limit 1for existence checks). - Act+verify in one call:
peek action --verify diffreturns just the delta — usually 10x smaller than--verify tree. - Shortcuts (⌘S, Esc, arrows, F-keys): use
peek key, not menu navigation. - Menu items:
peek menu --click "Save"for menu BAR;peek action --do Pressonly works for items in an already-open menu.
Window targeting
All UI commands accept one of: --app NAME (case-insensitive substring), --pid PID, or a positional <window-id>. --app is simplest. Doesn't apply to launch / quit (use --bundle-id / --name).
For coordinate ops (click/drag/scroll) with a target set, peek verifies the point lands on that app/window — it raises an occluded target window, or errors (x, y) is over '<OtherApp>' if the coordinates are stale or over another window. On that error, re-read frames with peek find (windows move/resize) or pass a specific <window-id> for multi-window apps.
Window-less apps (Dock, Control Center, status-menu helpers): --app NAME or --pid scopes find/tree/action to the AXApplication root. Not in plain peek apps — go straight to peek find --app Dock --role AXDockItem (peek apps --include-panels does list the ones owning panels/status items).
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 Changed · +5 lines 0bdfcd50c72c
- 8d ago First seen · 155 lines · 51 tokens per session scan A 7c950419ab52
use-peek is a skill published in the GitHub repository alexmx/peek (5 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 3,072 once invoked, about $0.0003 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 skills, from other repositories
tauri-mcp-cli
Use the Tauri MCP CLI to start and recover driver sessions, automate Tauri webviews, capture UI state, debug IPC, and work with mobile or remote devices. Use whenever an agent needs to operate a Tauri v2 app from terminal commands.
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
browser-edge-cases
SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.
atmos-introspection
Introspection & Querying: describe/list commands, config filtering, workspace introspection, dependency graphs, YQ integration, --help= scoped CLI help.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.
vs-search-tuning-partial-case
Use when the user provides 1-50 concrete bad-case search queries for one Viking Search app and wants local deterministic fixes. This skill only verifies request-level fine-operation interventions against a read-only baseline scene and delivers a console-ready configuration sheet, validated payloads, and a replay…