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.
git clone --depth 1 https://github.com/getsentry/XcodeBuildMCP-iOS-TemplateWrote 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/rules/getsentry/xcodebuildmcp-ios-template/swift-testing)<a href="https://agentmods.dev/rules/getsentry/xcodebuildmcp-ios-template/swift-testing"><img src="https://agentmods.dev/badge/rules/getsentry/xcodebuildmcp-ios-template/swift-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/rules/getsentry/xcodebuildmcp-ios-template/swift-testing"><img src="https://agentmods.dev/badge/rules/getsentry/xcodebuildmcp-ios-template/swift-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.00044 | $0.01471 |
| Opus 5.5 | $0.00018 | $0.00588 |
| Sonnet 5.5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00004 | $0.00147 |
Grade A, and why
swift-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 1mo 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: "Swift Testing Framework Guidelines" description: "Modern Swift Testing patterns with @Test macros, #expect/#require assertions, async testing, parameterized tests, and test organization. Apply when writing or modifying tests, setting up test suites, or working with test files." agent_requested: true applies_to: ["/Tests//*.swift", "/*Tests.swift", "/*Test.swift"]
Swift Testing Framework Guidelines
Modern Testing with @Test Macros
Use the Swift Testing framework (not XCTest) for all tests. Tests should be placed in MyProjectPackage/Tests.
Basic Test Structure
import Testing
@Test("User can successfully log in with valid credentials")
func userLogin() async throws {
let authService = AuthService()
let result = try await authService.login(
username: "testuser",
password: "validpassword"
)
#expect(result.isSuccess)
#expect(result.user.name == "Test User")
}
@Test("Login fails with invalid credentials")
func invalidLogin() async throws {
let authService = AuthService()
await #expect(throws: AuthError.invalidCredentials) {
try await authService.login(username: "", password: "")
}
}
Required Patterns
- Use @Test macro instead of XCTest's test prefix
- Use #expect and #require for assertions, not XCTAssert
- Include descriptive test names as string parameters
- Test async code with proper async/await patterns
- Use #require when test should stop on failure
Key Swift Testing Features
- @Test: Marks a test function (replaces XCTest's test prefix)
- @Suite: Groups related tests together
- #expect: Validates conditions (replaces XCTAssert)
- #require: Like #expect but stops test execution on failure
- Parameterized Tests: Use @Test with arguments for data-driven tests
- async/await: Full support for testing async code
- Traits: Add metadata like
.bug(),.feature(), or custom tags
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.
- 1mo ago First seen · 233 lines · 44 tokens per session scan A 24dd8184cd9d
swift-testing is a cursor rule published in the GitHub repository getsentry/XcodeBuildMCP-iOS-Template (42 stars, last pushed 1y ago), licensed MIT. It adds 44 tokens to every session and 1,471 once invoked, about $0.0002 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-08-30.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
common-fixes
Utility for VAN QA common validation fixes.