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 skills add rusel95/ios-agent-skills --skill ios-testinggit clone --depth 1 https://github.com/rusel95/ios-agent-skillsWrote 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/rusel95/ios-agent-skills/ios-testing)<a href="https://agentmods.dev/skills/rusel95/ios-agent-skills/ios-testing"><img src="https://agentmods.dev/badge/skills/rusel95/ios-agent-skills/ios-testing.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.1 | $0.00134 | $0.03865 |
| Opus 5 | $0.00067 | $0.01932 |
| Sonnet 5 | $0.00027 | $0.00773 |
| Haiku 4.5 | $0.00013 | $0.00386 |
Grade A, and why
ios-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 8d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Approach: F.I.R.S.T-First, Production-Ready Tests -- Every test produced by this skill must be Fast, Isolated, Repeatable, Self-validating, and Thorough. Architecture changes to production code and improvements to the test suite both follow phased, low-risk PRs tracked in a
refactoring/directory.
iOS Swift Testing
Enterprise-grade testing skill covering 11 areas across all iOS architectures. Opinionated: prescribes Swift Testing (@Test/@Suite/#expect) for all new tests on Xcode 16+, protocol-based mocks with call tracking, F.I.R.S.T compliance checks on every generated test, and architecture-specific patterns for MVVM (UIKit+Combine, SwiftUI+@Observable), VIPER, and TCA.
Test Distribution Rule
Target: 90% unit tests (mocked, milliseconds) | 8% integration (real DB/network stub) | 2% UI (XCUITest). When in doubt, write a unit test.
F.I.R.S.T Principles
| Principle | What it means | Violation signal |
|---|---|---|
| Fast | Unit tests should run in milliseconds. Avoid unnecessary waits. | Real URLSession, Thread.sleep, disk I/O |
| Isolated | Tests don't share state. Order doesn't matter. | static var, setUp skipped, test A breaks B |
| Repeatable | Same result on any machine, any time. | Date(), UUID(), random data, time zones |
| Self-validating | Pass or fail -- no log inspection. | print(result) with no assertion |
| Thorough | Happy path + error path + edge cases. | Only green-path tests, 0% error coverage |
Quick Decision Trees
"Swift Testing or XCTest?"
Need UI testing? -> XCTest (XCUITest) only
Need performance testing? -> XCTest (measure {}) only
Need attachments? -> XCTest only
Need ObjC support? -> XCTest only
New unit/integration test? -> Swift Testing (preferred)
Existing XCTest? -> Migrate incrementally, both coexist
"Which assertion macro?"
Soft check (report + continue)? -> #expect(expr)
Hard precondition (halt on fail)? -> try #require(expr)
Unwrap optional + use value? -> let val = try #require(optional)
Check error thrown? -> #expect(throws: Type.self) { }
Check nothing thrown? -> #expect(throws: Never.self) { }
Record unconditional failure? -> Issue.record("msg")
What ships with it
15 files 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.
- README.md 6.9 KB
- references/anti-patterns.md 7.4 KB
- references/async-testing.md 11 KB
- references/enterprise-testing.md 7.4 KB
- references/integration-testing.md 6.8 KB
- references/observable-testing.md 5.8 KB
- references/refactoring-workflow.md 6.9 KB
- references/rules.md 3.0 KB
- references/snapshot-testing.md 3.5 KB
- references/swift-testing-framework.md 16 KB
- references/tca-testing.md 5.6 KB
- references/test-organization.md 7.3 KB
- references/ui-testing.md 6.1 KB
- references/viper-testing.md 5.1 KB
- references/xctest-patterns.md 11 KB
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.
- 8d ago First seen · 256 lines · 134 tokens per session scan A 5517029c9cae
ios-testing is a skill published in the GitHub repository rusel95/ios-agent-skills (7 stars, last pushed 4mo ago), licensed MIT. It adds 134 tokens to every session and 3,865 once invoked, about $0.0007 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.
Other skills, from other repositories
ios-testing
MyAppTests/ # Unit test target Models/ UserTests.swift OrderTests.swift ViewModels/ LoginViewModelTests.swift ProfileViewModelTests.swift Services/ APIClientTests.swift AuthServiceTests.swift Helpers/ Mocks/ MockAPIClient.swift MockAuthService.swift TestData/ UserFixtures.swift JSONFixtures.swift MyAppUITests/ # UI…
ios-testing
Testing patterns for Swift and SwiftUI apps.
mobile-testing
Android and JVM testing - JUnit5, MockK, Turbine for Flow, and Compose UI testing for unit, integration, and UI tests; also applies to KMP commonTest running on the JVM/Android target. For iOS/Swift tests (XCTest, Swift Testing, XCUITest) use ios-testing. For TDD methodology and the three-tier test model (fake-first…
aidex-coverage
Use when writing, placing, or running tests in any project — which layer a behaviour belongs in ("unit or E2E for X", "component test or browser test"), which tests to run for a change instead of the whole suite, when to extract a fixture, setting up an isolated disposable E2E environment, or the per-project testing…
ui-crawler-max
Autonomous UI crawler for iOS simulator apps — rapid, element-precise data collection. Use whenever the user says "crawl my app", "auto-test the UI", "click/tap through every screen", "monkey test", "explore the app and find errors/crashes", "collect screenshots of all screens", "smoke test the whole app", or asks for…
swift-testing
Build an Apple-platform test strategy with Swift Testing for unit and integration coverage, XCTest for UI automation, deterministic fixtures, and concise agent-readable results.