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 CarolaneLFBV/ios-development-agents --skill ios-testinggit clone --depth 1 https://github.com/CarolaneLFBV/ios-development-agentsWrote 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/carolanelfbv/ios-development-agents/ios-testing)<a href="https://agentmods.dev/skills/carolanelfbv/ios-development-agents/ios-testing"><img src="https://agentmods.dev/badge/skills/carolanelfbv/ios-development-agents/ios-testing/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/carolanelfbv/ios-development-agents/ios-testing"><img src="https://agentmods.dev/badge/skills/carolanelfbv/ios-development-agents/ios-testing.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.00026 | $0.00387 |
| Opus 5.5 | $0.00010 | $0.00155 |
| Sonnet 5.5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00003 | $0.00039 |
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 today.
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
Testing
Inspect the actual test target, toolchain and existing suites. Determine Swift Testing compatibility from its toolchain/runtime requirements, not an arbitrary app deployment cutoff. Verify unfamiliar testing APIs in official documentation.
- Prefer Swift Testing for suitable new unit tests; preserve existing XCTest suites. Use XCTest/XCUITest for UI and XCTest performance measurements. Both frameworks can coexist, but do not mix their assertion/lifecycle APIs in one test.
- Test observable behavior, failure paths and meaningful state transitions. Avoid tests of trivial accessors, framework internals, or implementation wording. Follow the project's coverage policy.
- For snapshot tests, inspect the installed provider, its rendering environment and baseline policy before choosing APIs or adding dependencies. Record device/OS, appearance, locale and text size for meaningful comparisons.
- Swift Testing runs tests in parallel by default. Isolate fixtures, databases,
clocks and network doubles. Use
@MainActorfor UI-isolated fixtures; serialize only when a shared resource genuinely requires it. - Synchronize async tests with controllable dependencies or supported expectations.
Creating a
Taskand immediately asserting a loading flag is racy. Avoid sleeps as a substitute for a deterministic readiness signal. - Use a fresh SwiftData container per isolated store test and keep it alive for the test. Test migrations with old on-disk stores; in-memory tests do not cover them.
- Discover the real scheme, test plan and installed simulator before invoking
xcodebuild. Useswift testonly for compatible package targets.
Work directly without recursive delegation. Report commands, actual test results, measured coverage and blockers. Distinguish generated tests from executed tests.
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.
- today First seen · 34 lines · 26 tokens per session scan A b41cdd82c8ef
ios-testing is a skill published in the GitHub repository CarolaneLFBV/ios-development-agents (7 stars, last pushed yesterday), licensed MIT. It adds 26 tokens to every session and 387 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-17.
Other skills, from other repositories
flutter-testing-skill
Generates Flutter widget tests, integration tests, and golden tests in Dart. Supports local execution and TestMu AI cloud for real device testing. Use when user mentions "Flutter", "widget test", "WidgetTester", "testWidgets", "fluttertest", "integrationtest". Triggers on: "Flutter", "widget test", "Dart test"…
mobiai-android-testing
Use when writing or running tests in an Android project — unit tests, UI tests, choosing the right framework and patterns.
cometchat-flutter-v6-testing
Test a Flutter app that uses the CometChat UI Kit — what is worth testing versus what belongs to the kit, mocking the SDK boundary, widget tests around chat screens, and integration/CI setup. Triggers: 'test my cometchat integration', 'mock cometchat in flutter tests', 'widget test chat screen', 'cometchat test setup'.
cometchat-ios-testing
Test an iOS app that embeds CometChat — what to mock vs exercise for real, keeping the CometChatSDK off the network in unit tests, waiting out the async init→login gate, and a lean XCUITest smoke. Triggers: 'test cometchat ios', 'unit test chat swift', 'mock cometchatsdk', 'xcuitest for chat', 'how do I test cometchat…
cometchat-react-native-testing
Test a CometChat React Native integration — mock the SDK for Jest unit tests, assert init-before-render ordering and no-Auth-Key-in-source, and use Detox for the flows only a device can prove. Triggers: test CometChat React Native, mock CometChat SDK jest, detox CometChat, unit test chat screen RN, CI tests for chat.
flutter-testing
Use when testing Flutter code - unit tests for logic, widget tests for UI behavior, golden tests for appearance, the multi-size/text-scale/dark matrix, accessibility guidelines, test-first.