Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mwd1234/ios-agentic-skillsnpx agentmods add skills/mwd1234/ios-agentic-skills/testing-strategyWrote 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/mwd1234/ios-agentic-skills/testing-strategy)<a href="https://agentmods.dev/skills/mwd1234/ios-agentic-skills/testing-strategy"><img src="https://agentmods.dev/badge/skills/mwd1234/ios-agentic-skills/testing-strategy/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/mwd1234/ios-agentic-skills/testing-strategy"><img src="https://agentmods.dev/badge/skills/mwd1234/ios-agentic-skills/testing-strategy.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.00035 | $0.00584 |
| Opus 5 | $0.00017 | $0.00292 |
| Sonnet 5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
testing-strategy 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Strategy
Build confidence across core flows with a layered test approach. Focus on deterministic logic, stable UI flows, and regression coverage.
When to use this skill
- Before App Store submission
- When adding a new feature or ViewModel
- After refactors touching haptics, timers, or syncing
- When flaky UI tests appear
Test Layers
1) Unit Tests (Fast, deterministic)
Targets: ViewModels, Managers, Models, Utilities
Checklist:
- Pure logic in Models/Utilities has unit tests
- ViewModels tested for state transitions
- Async flows tested with
XCTestExpectation - Watch sync logic tested with mock
WCSession
Suggested patterns:
- Dependency injection via protocols
- Use fakes/stubs for haptics, timers, clock
2) UI Tests (Critical flows only)
Targets: Core journeys and regressions
Recommended flows:
- Start/stop timer
- Edit haptic pattern
- Save/restore presets
- Watch ↔ Phone sync path (smoke test)
3) Snapshot / Visual Regression (Optional)
Use snapshots for stable screens (settings, templates, empty states). Avoid animation-heavy views.
Coverage Map (Suggested)
| Area | Minimum Coverage | Notes |
|---|---|---|
| ViewModels | 80%+ | Highest ROI tests |
| Managers | 70%+ | Haptics, timers, storage |
| Views | Key flows | UI test smoke coverage |
| Watch sync | Basic | Validate payload and fallback |
| Localization | Automated | Ensure no missing keys |
Test Hygiene
- Avoid hardcoded dates; inject clocks
- Avoid timers in tests; inject schedulers
- Use
@MainActorfor UI-bound tests - Keep UI tests under 3–5 critical paths
Localization Regression
Run localization scripts as part of CI or before release:
python3 scripts/check_localization_status.py YourApp/Localizable.xcstrings
python3 scripts/check_localization_status.py YourApp/AppIntents/AppShortcuts.xcstrings
python3 scripts/check_localization_status.py "YourApp Watch App/Localizable.xcstrings"
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 · 93 lines · 35 tokens per session scan A e38a9ffc22e1
testing-strategy is a skill published in the GitHub repository mwd1234/ios-agentic-skills (50 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 584 once invoked, about $0.0002 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
android_ui_verification
Automated end-to-end UI testing and verification on an Android Emulator using ADB.
solopi-ai
A command-line framework for testing Android apps and devices with SoloPi, including on-device or cloud AI decision models. It manages devices, test cases, recorded interactions, replays, performance history, and evidence.
agent-device
Automates Apple-platform apps (iOS, tvOS, macOS), Android devices, and Amazon Vega OS TV apps in Vega Virtual Devices. Use when navigating apps, taking snapshots/screenshots where supported, driving TV remotes, tapping, typing, scrolling, extracting UI info, collecting evidence, or planning agent-device CLI commands.
ios-simulator
Verify and debug native, React Native, Expo, or Flutter apps on an iOS Simulator with agent-device. Use when an agent needs to launch an app, inspect its live UI, tap, type, scroll, validate a code change, collect failure evidence, or reproduce a workflow on an iPhone or iPad Simulator.
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
eas-simulator
EAS service (paid). Run and control a user's app on a remote iOS/Android simulator hosted on EAS cloud. Read before running any eas simulator: commands - it has the current syntax for this experimental API. Use whenever the user needs a simulator they can't run locally - 'run my app on a cloud simulator', 'use eas…