ui-automation

A skill for controlling an app through the device's visible screen, using clicks, scrolling, typing, and navigation.

In plain words
What is it for?
Use it to open apps, inspect their current screen, find controls, click buttons or links, scroll, and enter text.
Why use it?
It lets an agent operate apps that do not provide a direct programming interface.

Skill for Claude CodeCodex

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 skills/vneel-code/ghost/ui-automation
Any agent
npx skills add vNeeL-code/GHOST --skill ui-automation
Clone the repo
git clone --depth 1 https://github.com/vNeeL-code/GHOST

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 167 The whole file, excluding the scripts and references it only reads on demand.
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.00023 $0.00167
Opus 5 $0.00012 $0.00084
Sonnet 5 $0.00005 $0.00033
Haiku 4.5 $0.00002 $0.00017

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

Security

Grade A, and why

ui-automation 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 3d 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.

app/src/main/assets/skills/ui-automation/SKILL.md · 21 lines

What it actually says

UI Automation Skill

You can control the physical screen of the device using accessibility hooks.

Guidelines

  1. Always start by calling dumpScreenState() to understand the current layout.
  2. Use clickUIElement(text="...") to interact with buttons or links.
  3. If an element is not visible, use scrollScreen("DOWN") to find it.
  4. If the app is not open, use performNavigation("HOME") first.
  5. Provide a brief one-sentence summary of the action you took.

Tools Available

  • clickUIElement
  • scrollScreen
  • performNavigation
  • dumpScreenState
  • typeText
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. 3d ago First seen · 21 lines · 23 tokens per session scan A a17f0877bf50

Subscribe to this mod's changes

ui-automation is a skill published in the GitHub repository vNeeL-code/GHOST (162 stars, last pushed 3d ago), licensed MIT. It adds 23 tokens to every session and 167 once invoked, about $0.0001 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-30.

Related

Other skills, from other repositories

computer-use

Read and drive native desktop applications through the accessibility layer — list on-screen apps, snapshot one window as a numbered element tree, then click / type / set a value / scroll / drag / run a named action, by element index or by screen coordinates. Use for work in a desktop app rather than a web page. Full…

kirodotdev/KiroCrew · 105 tokens

feature-demo-recording

Record a demo video of a web feature from a real browser. Two modes -- a NARRATED film where measured voiceover drives the timeline (designed slides, subtitles, punch-in camera, rendered from an HTML timeline), and a SILENT evidence clip for a PR or a QA pass. Use when the user asks to record a video, demo, or screen…

kirodotdev/KiroCrew · 90 tokens

browser-recording

Record a browser flow as a video/GIF for evidence — animations, transitions, and multi-step interactions that a still screenshot cannot prove. Drives the project's own Playwright through a bundled runner, then converts to mp4 + GIF via ffmpeg. Use when the user asks to record a demo, capture a GIF or video of the UI…

kirodotdev/KiroCrew · 85 tokens

web-browse

Open a REAL external web page so the user can see it in Kiro Crew's Browser panel. PRIMARY path is the browser MCP tool (drives the built-in native panel); playwright-cli is the fallback for remote/plain-browser sessions and for attached logged-in browsers. Use when the user wants to VIEW / verify / "show me" an…

kirodotdev/KiroCrew · 93 tokens

web-verify

Look at your OWN front-end change before claiming it works -- navigate the loopback URL of a dev server or pod you started, screenshot the surface you changed, read the image to judge it, and embed it in chat. Three capture backends: playwright-cli (the session the dashboard Browser panel shows), the agent-browser CLI…

kirodotdev/KiroCrew · 0 tokens

browser-auth

Browse sites that need a logged-in session with playwright-cli, using attach mode, saved storage state, or individual cookies. Use when a page is behind a login wall and a plain open lands on a sign-in screen.

kirodotdev/KiroCrew · 47 tokens