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.
npx agentmods add skills/conorluddy/xclaude-plugin/ios-testing-patternsnpx skills add conorluddy/xclaude-plugin --skill ios-testing-patternsgit clone --depth 1 https://github.com/conorluddy/xclaude-pluginWrote 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/conorluddy/xclaude-plugin/ios-testing-patterns)<a href="https://agentmods.dev/skills/conorluddy/xclaude-plugin/ios-testing-patterns"><img src="https://agentmods.dev/badge/skills/conorluddy/xclaude-plugin/ios-testing-patterns.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.04619 |
| Opus 5 | $0.00009 | $0.02309 |
| Sonnet 5 | $0.00004 | $0.00924 |
| Haiku 4.5 | $0.00002 | $0.00462 |
Grade A, and why
ios-testing-patterns 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 4d 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 — 898 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Testing Patterns Skill
Comprehensive guide to XCTest and XCUITest execution, analysis, and flaky test detection
Overview
This skill provides patterns and workflows for executing iOS tests using XCTest and XCUITest frameworks. It covers test execution strategies, result analysis, flaky test detection, and troubleshooting common test failures.
Use this skill when:
- Running unit tests or UI tests
- Analyzing test failures
- Detecting and debugging flaky tests
- Optimizing test execution performance
- Setting up CI/CD test pipelines
Quick Reference
| Task | Operation | Key Parameters |
|---|---|---|
| Run all tests | test |
scheme, destination |
| Run specific test | test |
scheme, only_testing |
| Skip tests | test |
scheme, skip_testing |
| Use test plan | test |
scheme, test_plan |
| Parallel execution | test |
destination (multiple) |
When to Use This Skill
Use ios-testing-patterns when:
- Executing XCTest unit tests
- Running XCUITest UI automation tests
- Investigating test failures
- Detecting intermittent test failures (flaky tests)
- Analyzing test performance and execution time
- Setting up test schemes and test plans
- Configuring parallel test execution
- Debugging test-specific simulator issues
Related Skills:
- xcode-workflows: For general build and test operations
- simulator-workflows: For managing test simulators
- ui-automation-workflows: For UI test interaction patterns
Key Concepts
XCTest vs XCUITest
XCTest (Unit/Integration Tests):
- Fast execution (milliseconds to seconds)
- Tests individual components in isolation
- Direct access to app internals
- No UI interaction required
- Runs in same process as app code
XCUITest (UI Tests):
- Slower execution (seconds to minutes)
- Tests user-facing workflows
- Black-box testing (no app internals)
- Requires simulator/device UI
- Runs in separate process
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.
- 4d ago First seen · 898 lines · 18 tokens per session scan A fcdb17db3b65
ios-testing-patterns is a skill published in the GitHub repository conorluddy/xclaude-plugin (182 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 4,619 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.
Other skills, from other repositories
rn-write-tests
Use to write tests for an Expo + RN app: Jest + React Native Testing Library for unit/integration (components, hooks, queries, mutations) and Maestro for end-to-end flows (sign-in, navigation, forms). Sets up the testing stack on first call (jest-expo preset, RNTL, jest config) and writes a focused test next to the…
test-flutter
Flutter App のテスト実行・静的解析・フォーマット・テスト記述ガイド.
check-and-test
Run lint checks (ruff for Python, Biome for TS/JS), type checks (pyright for Python, tsc for TS/JS), and the standard pytest tiers (unit + e2e + tests skipped during pre-commit). Investigates failures to determine if they are application bugs or test issues, and fixes application bugs rather than weakening tests. Does…
testing
Writes and documents the test suite for a generated cli-web- CLI (Phase 3): unit tests with mocked HTTP, live E2E tests, subprocess tests via resolvecli, and the TEST.md plan/results record. Use after the methodology skill completes implementation.
testing-assistant
Manages testing lifecycle including unit tests, integration tests, validation, and quality assurance.
platform-specialist
Doc-driven platform integration expert. Converts a web app to LINE MINI App (LIFF SDK), PWA (Next.js 16), and Capacitor (iOS/Android). Expo & Tauri are secondary/legacy. ปรัชญาหลัก: ดึง docs จริงล่าสุดก่อนเขียนโค้ดเสมอ — ไม่ freeze snippet ที่จะ rot. Triggers: "LINE MINI App", "LIFF", "LINE OA", "convert to app"…