Borrowing it
Nothing to install: this file belongs to PowerBeef/Vocello. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/PowerBeef/Vocello/main/.claude/skills/vocello-ui-autonomy/SKILL.mdgit clone --depth 1 https://github.com/PowerBeef/VocelloWrote 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/powerbeef/vocello/vocello-ui-autonomy)<a href="https://agentmods.dev/skills/powerbeef/vocello/vocello-ui-autonomy"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-ui-autonomy/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/powerbeef/vocello/vocello-ui-autonomy"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-ui-autonomy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00054 | $0.01020 |
| Opus 5.5 | $0.00022 | $0.00408 |
| Sonnet 5.5 | $0.00011 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
vocello-ui-autonomy 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous UI checks beyond XCUITest
Goal: $ARGUMENTS
Read docs/reference/development-workflow.md (Computer use) and the routing table in docs/reference/ios-device-testing.md. Maintainer decisions of 2026-10-25: XCUITest stays the only automated evidence; computer use is the default route for everything it cannot cover; a computer-use record closes an attended row only when the maintainer confirms it; phone work happens only in a window the maintainer announced; Claude never changes a system or security setting, grants a permission, enters a passcode or credential, deletes the app or confirms a purchase.
Route each check
- XCUITest can drive it (app UI with stable identifiers): use
scripts/ui_test.sh(skillvocello-ios-validationorvocello-macos-ui), then review the run's screenshots (below). - XCUITest cannot, and the check survives Mirroring's conditions (UI flows, in-app settings, model management, TestFlight installs, reproductions, visual inspection): computer use.
- Maintainer by hand: anything needing an iPhone system setting (Wi-Fi off, airplane mode, Auto-Lock, Low Data Mode, Developer Mode, UI Automation), a permission prompt, the passcode or Face ID, the microphone or camera, audio routing or interruptions (Mirroring sends audio to the Mac), VoiceOver, app deletion, a purchase confirmation. Pause and notify (below).
Window protocol (iPhone)
- Setup card, sent once at the window's start: Wi-Fi and Bluetooth on (both devices); Auto-Lock as the rows need; Developer Mode and UI Automation on; a Focus on so notifications stay out of screenshots; the build to test installed; Screen Recording allowed once for the capturing app; the phone unlocked.
- Block A, lanes:
scripts/ios_device.sh mirroring stop, then every XCUITest lane in scope. The lanes'ui-preflightrefuses while iPhone Mirroring runs, because XCUITest breaks under it. - Handoff: ask the maintainer to lock the phone (Mirroring needs it locked; unlocking ends Mirroring).
- Block B, Mirroring:
scripts/ios_device.sh mirroring status, thenscripts/ios_device.sh mirroring session <label>;request_accessfor "iPhone Mirroring";open_application"iPhone Mirroring"; screenshot before every action; act; after each meaningful stepscripts/ios_device.sh mirroring capture <label> --step "<action>" --observed "<what shows>"; verify before moving on. - Close:
scripts/ios_device.sh mirroring stop; report each record (folder under build/artifacts/ios/mirroring) for the maintainer's confirmation; never claim a row closed before it.
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.
- 3d ago First seen · 67 lines · 54 tokens per session scan A 9e90ab2f0e83
vocello-ui-autonomy is a skill published in the GitHub repository PowerBeef/Vocello (386 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,020 once invoked, about $0.0002 per session on Opus 5.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-10-26.
Other skills, from other repositories
ios-simulator-ui-automation
Drive a booted iOS Simulator like a user with the axe CLI (describe-ui, tap, swipe, type, screenshot, record-video) to verify UI flows, reproduce bugs and capture screenshots. Use when asked to tap, scroll, type into, screenshot or smoke-test a running iOS app.
android-ui-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
swift-concurrency-pro
Reviews Swift code for concurrency correctness, modern API usage, and common async/await pitfalls. Use when reading, writing, or reviewing Swift concurrency code.
eas-simulator
Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas simulator to…