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-ios-validation/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-ios-validation)<a href="https://agentmods.dev/skills/powerbeef/vocello/vocello-ios-validation"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-ios-validation/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-ios-validation"><img src="https://agentmods.dev/badge/skills/powerbeef/vocello/vocello-ios-validation.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.00035 | $0.00402 |
| Opus 5.5 | $0.00014 | $0.00161 |
| Sonnet 5.5 | $0.00007 | $0.00080 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
vocello-ios-validation 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.
What it actually says
iOS validation
Arguments: $ARGUMENTS
Read docs/reference/native-engineering.md, docs/reference/ios-device-testing.md and
the applicable Axiom build/testing guidance. Commands run from the repository root.
Use scripts/dev.sh ios for a generic device-SDK compile. Choose the smallest relevant existing
lane from scripts/ui_test.sh help for physical-iPhone acceptance; do not substitute another driver.
Before a measured lane join/stop all workers, commit the checkpoint, use scripts/dev.sh doctor,
and probe reachability with python3 scripts/lib/ios_coredevice_probe.py probe; never print device IDs.
Before any phone lane quit iPhone Mirroring (scripts/ios_device.sh mirroring stop): XCUITest breaks
under it and ui-preflight refuses while it runs; the phone must then be unlocked.
When lifecycle tracking is unavailable, declare QVOICE_LEAD_ONLY=1 only after joining all workers.
Explain the lane and expected device interaction, then run scripts/ui_test.sh ios <lane> <options>.
Use installed models; new large downloads need specific authorization. Preserve failed artifacts.
Read scripts/dev.sh triage <run-directory> --json (the read-only vocello-xcresult-triage agent can
take the run directory); report the actual verdict and evidence path.
Never retry silently; a justified rerun gets a new ID and explanation. No Simulator or third-party
UI-automation MCP; computer use through iPhone Mirroring covers what XCUITest cannot, never during a
lane (/vocello-ui-autonomy). After the lane, review <run>/screenshots/index.json.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +4 lines 203dac6d4b65
- 16d ago Changed · +4 lines 642ac61851ce
- 18d ago First seen · 19 lines · 35 tokens per session scan A d3340fe2b4de
vocello-ios-validation is a skill published in the GitHub repository PowerBeef/Vocello (386 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 402 once invoked, about $0.0001 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-11.
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…