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.
git clone --depth 1 https://github.com/yusufkaran/swiftui-autotest-skillWrote 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/plugins/yusufkaran/swiftui-autotest-skill/swiftui-autotest-skill)<a href="https://agentmods.dev/plugins/yusufkaran/swiftui-autotest-skill/swiftui-autotest-skill"><img src="https://agentmods.dev/badge/plugins/yusufkaran/swiftui-autotest-skill/swiftui-autotest-skill/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/plugins/yusufkaran/swiftui-autotest-skill/swiftui-autotest-skill"><img src="https://agentmods.dev/badge/plugins/yusufkaran/swiftui-autotest-skill/swiftui-autotest-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
swiftui-autotest-skill 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 9d 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
{
"name": "swiftui-autotest-skill",
"version": "1.0.0",
"description": "AI-powered visual testing and accessibility setup for iOS/SwiftUI apps. Build, launch in Simulator, test with computer use, detect crashes, analyze memory leaks, and add accessibility identifiers.",
"author": {
"name": "Yusuf Karan"
},
"repository": "https://github.com/yusufkaran/swiftui-autotest-skill",
"license": "MIT",
"keywords": [
"ios",
"swiftui",
"testing",
"accessibility",
"simulator",
"computer-use",
"memory-leak",
"performance",
"xcode"
],
"commands": [
"./commands"
],
"skills": [
"./skills/ios-test",
"./skills/add-accessibility"
],
"postinstall": "./postinstall.sh"
}
What it installs
The manifest is a name and a version. 3 skills, 2 commands travel with it, and installing the plugin installs all of them — 302 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 9d ago First seen · 30 lines scan A 0bb1c4972081
swiftui-autotest-skill is a plugin published in the GitHub repository yusufkaran/swiftui-autotest-skill (24 stars, last pushed 5mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
aco
Drive a live Appium session from Claude Code with the aco CLI — start/stop sessions, find elements, tap, swipe, type, screenshot, read page source, switch web contexts, and call platform mobile: extensions on iOS simulators/emulators and real devices.
maestro-testing
Generate and manage Maestro test flows for mobile (Android, iOS) and web apps. Covers React Native, Expo, Flutter, Swift, Kotlin, Jetpack Compose, SwiftUI, UIKit, Capacitor, Ionic, and web desktop testing.
ios-simulator-skill
29 production-ready scripts for iOS app testing, building, and automation. Provides semantic UI navigation, build automation, accessibility testing, and simulator lifecycle management.
zmr
Agent-native mobile UI automation and verification for Expo, React Native, Flutter, and native Android/iOS apps. Gives Claude Code eyes and hands on emulators and simulators: semantic snapshots, typed actions, waits, assertions, and replayable traces.
mobile-app-testing
Test your web app on real iOS Simulator / Android emulator sessions via tapflow, alongside your existing Playwright suite.
qa-explore
A team of AI agents that test any web app like human QA: explore the live app, screenshot and visually judge rendering + data, capture trace/HAR/console/video evidence, adversarially verify findings, learn from rejected ones, codify them into a self-growing Playwright/Cypress suite — and close the loop by filing…