agentmods.dev

device-testing

device-testing is a skill for Claude Code, Codex from troyjthomas/ios-agent-skills. It costs 51 tokens per session (1,338 once invoked), scanned A, original, MIT.

A final testing guide for checking an iPhone app on physical Apple devices before TestFlight or App Store release. It covers automated checks in Xcode and manual checks that a simulator cannot reproduce.

In plain words
What is it for?
Use it before release to run tests, build for a simulator, connect a real iPhone, inspect the app manually, and verify accessibility and device behavior.
Why use it?
It catches hardware-specific layout, touch, accessibility, and interaction problems that may be missed in a simulator. It also checks for build errors, broken imports, and failing unit tests.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code.

not rated 2 3mo ago A scan 51 tokens original MIT
View the source file troyjthomas/ios-agent-skills
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/troyjthomas/ios-agent-skills/device-testing
Any agent
npx skills add troyjthomas/ios-agent-skills --skill device-testing
Clone the repo
git clone --depth 1 https://github.com/troyjthomas/ios-agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for device-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/troyjthomas/ios-agent-skills/device-testing.svg)](https://agentmods.dev/skills/troyjthomas/ios-agent-skills/device-testing)
Your own site
<a href="https://agentmods.dev/skills/troyjthomas/ios-agent-skills/device-testing"><img src="https://agentmods.dev/badge/skills/troyjthomas/ios-agent-skills/device-testing.svg" alt="Measured on agentmods" height="20"></a>
Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,338 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.1 $0.00051 $0.01338
Opus 5 $0.00026 $0.00669
Sonnet 5 $0.00010 $0.00268
Haiku 4.5 $0.00005 $0.00134

Measured 5d ago against content hash dfc9b8fe6216, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

device-testing 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 5d 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.

skills/device-testing/SKILL.md · 174 lines

How it starts

The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Device Testing

Simulator is not enough. Real devices reveal real problems.

When to Use

  • Polish phase is complete
  • You're preparing for TestFlight distribution
  • You want to verify the app before showing it to anyone
  • You're doing a final check before App Store submission

Prerequisites

  • iPhone connected to your Mac via USB or on the same Wi-Fi
  • Apple Developer account (free account works for personal device testing)
  • Device added in Xcode (Window > Devices and Simulators)

Automated Testing with XcodeBuildMCP

Before manual device testing, run automated checks via Claude Code:

Run all unit tests using XcodeBuildMCP. Report any failures.
Build for the iPhone 16 Pro simulator and verify no warnings.

This catches regressions and compile issues before you invest time in manual testing. Claude Code can also fix failing tests and re-run them in a loop.

What Automated Tests Catch

  • Compile errors across all build configurations
  • Unit test failures (logic, data model, state management)
  • Missing file references or broken imports

What Only Manual Testing Catches

  • Visual layout issues on real hardware
  • Touch interaction feel (haptics, gesture responsiveness)
  • Performance on actual iPhone hardware (not Mac CPU)
  • Camera, GPS, and sensor-dependent features
  • Real keyboard behavior vs simulator keyboard passthrough

Installing on Device

In Xcode:

  1. Select your connected iPhone as the run destination
  2. Press Cmd+R to build and run
  3. First time: trust the developer certificate on the iPhone (Settings > General > VPN & Device Management)

Tell Claude Code if you need help:

Help me configure Xcode to run the app on my physical iPhone.
Set the development team in Signing & Capabilities.

The Testing Script

Work through these systematically. Take notes on anything that feels wrong.

Core Flow Testing

  1. First launch experience
    • Kill the app. Delete it. Reinstall fresh
    • Does the onboarding appear?
    • Can you complete setup without confusion?
    • After onboarding, is the empty state clear?

Read the full file on GitHub · 174 lines

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. 5d ago First seen · 174 lines · 51 tokens per session scan A dfc9b8fe6216

Subscribe to this mod's changes

device-testing is a skill published in the GitHub repository troyjthomas/ios-agent-skills (2 stars, last pushed 3mo ago), licensed MIT. It adds 51 tokens to every session and 1,338 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.

MobileTestingagent-skillsai-codingappleclaude-codefigmaios-development
Related

Other skills, from other repositories

activitykit

Implement, review, or improve Live Activities and Dynamic Island experiences in iOS apps using ActivityKit. Use when building real-time updating widgets for the Lock Screen and Dynamic Island — delivery tracking, sports scores, ride-sharing status, workout timers, media playback, or any time-sensitive information that…

dpearson2699/swift-ios-skills · 105 tokens

carplay

Build CarPlay-enabled apps using the CarPlay framework. Use when creating navigation, audio, communication, EV charging, parking, or food ordering apps for the car display, working with CPTemplateApplicationScene, CPInterfaceController template hierarchies, CPListTemplate, CPMapTemplate, CPNowPlayingTemplate…

dpearson2699/swift-ios-skills · 80 tokens

cloudkit

Implement, review, or improve CloudKit and iCloud sync in iOS/macOS apps. Use when working with CKContainer, CKRecord, CKQuery, CKSubscription, CKSyncEngine, CKShare, NSUbiquitousKeyValueStore, or iCloud Drive file coordination; when syncing SwiftData models via ModelConfiguration with cloudKitDatabase; when handling…

dpearson2699/swift-ios-skills · 102 tokens

financekit

Access eligible Wallet financial data using FinanceKit and FinanceKitUI. Use when querying transactions or balances, reading Apple Card, Apple Cash, Savings, or U.K. connected-account data, requesting financial-data authorization, using TransactionPicker, enabling iOS 26 background delivery, or saving and checking…

dpearson2699/swift-ios-skills · 64 tokens

ios-accessibility

Build and audit SwiftUI, UIKit, and AppKit accessibility for VoiceOver, Voice Control, Switch Control, Full Keyboard Access, Dynamic Type, focus restoration, labels/traits/actions, traversal, custom rotors, NSAccessibility, XCTest checks, adaptive system preferences, and App Store accessibility declarations. Use when…

dpearson2699/swift-ios-skills · 91 tokens

push-notifications

Implement, review, or debug push notifications in iOS/macOS apps — local notifications, remote (APNs) notifications, rich notifications, notification actions, silent pushes, and notification service/content extensions. Use when working with UNUserNotificationCenter, registering for remote notifications, handling…

dpearson2699/swift-ios-skills · 102 tokens