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 rules/steipete/agent-rules/swift-testing-playbookgit clone --depth 1 https://github.com/steipete/agent-rulesWhat 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.00000 | $0.05978 |
| Opus 5 | $0.00000 | $0.02989 |
| Sonnet 5 | $0.00000 | $0.01196 |
| Haiku 4.5 | $0.00000 | $0.00598 |
Grade A, and why
swift-testing-playbook 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- swift-testing-playbook — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 454 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The Ultimate Swift Testing Playbook (2024 WWDC Edition, expanded with Apple docs from June 2025)
https://developer.apple.com/xcode/swift-testing/
A hands-on, comprehensive guide for migrating from XCTest to Swift Testing and mastering the new framework. This playbook integrates the latest patterns and best practices from WWDC 2024 and official Apple documentation to make your tests more powerful, expressive, and maintainable.
1. Migration & Tooling Baseline
Ensure your environment is set up for a smooth, gradual migration.
| What | Why |
|---|---|
| Xcode 16 & Swift 6 | Swift Testing is bundled with the latest toolchain. It leverages modern Swift features like macros, structured concurrency, and powerful type-system checks. |
| Keep XCTest Targets | Incremental Migration is Key. You can have XCTest and Swift Testing tests in the same target, allowing you to migrate file-by-file without breaking CI. Both frameworks can coexist. |
| Enable Parallel Execution | In your Test Plan, ensure "Use parallel execution" is enabled. Swift Testing runs tests in parallel by default, which dramatically speeds up test runs and helps surface hidden state dependencies that serial execution might miss. |
Migration Action Items
- Ensure all developer machines and CI runners are on macOS 15+ and Xcode 16+.
- For projects supporting Linux/Windows, add the
swift-testingSPM package to yourPackage.swift. It's bundled in Xcode and not needed for Apple platforms. - For existing test targets, you must explicitly enable the framework. In the target's Build Settings, find Enable Testing Frameworks and set its value to Yes. Without this,
import Testingwill fail. - In your primary test plan, confirm that “Use parallel execution” is enabled. This is the default and recommended setting.
2. Expressive Assertions: #expect & #require
Replace the entire XCTAssert family with two powerful, expressive macros. They accept regular Swift expressions, eliminating the need for dozens of specialized XCTAssert functions.
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.
- yesterday First seen · 454 lines · 0 tokens per session scan A 7199aeb7d6ce
swift-testing-playbook is a cursor rule published in the GitHub repository steipete/agent-rules (5,696 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,978 tokens. 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 cursor rules, from other repositories
android_unit_testing_bdd
Unit testing best practices with BDD style.
android_general_rules
For every Kotlin Android code you generate or refactor.
android_integration_testing
Android Integration Testing best practices for multi-layer testing.
android_workmanager_best_practices
Best practices for WorkManager usage in background tasks.
android_naming_conventions
Naming conventions for consistency.
react_hooks
React Hooks best practices for frontend package.