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 OkminLee/everything-claude-code-ios --skill swift-tdd-workflowgit clone --depth 1 https://github.com/OkminLee/everything-claude-code-iosWrote 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/okminlee/everything-claude-code-ios/swift-tdd-workflow)<a href="https://agentmods.dev/skills/okminlee/everything-claude-code-ios/swift-tdd-workflow"><img src="https://agentmods.dev/badge/skills/okminlee/everything-claude-code-ios/swift-tdd-workflow.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.00043 | $0.03904 |
| Opus 5 | $0.00022 | $0.01952 |
| Sonnet 5 | $0.00009 | $0.00781 |
| Haiku 4.5 | $0.00004 | $0.00390 |
Grade B, and why
swift-tdd-workflow scanned grade B with 1 finding 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 7d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
run: sudo xcode-select -s /Applications/Xcode_15.2.app How it starts
The opening of the file, as written. The whole thing — 695 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift Test-Driven Development Workflow
This skill ensures all iOS development follows TDD principles with comprehensive test coverage.
When to Activate
- Writing new features or functionality
- Fixing bugs or issues
- Refactoring existing code
- Adding API integrations
- Creating new SwiftUI views or UIKit components
Core Principles
1. Tests BEFORE Code
ALWAYS write tests first, then implement code to make tests pass.
2. Coverage Requirements
- Minimum 80% coverage (unit + integration + UI)
- All edge cases covered
- Error scenarios tested
- Boundary conditions verified
3. Test Types
Unit Tests (XCTest)
- Individual functions and methods
- ViewModels and business logic
- Pure functions
- Helpers and utilities
Integration Tests
- API client operations
- Database operations
- Service interactions
- External API calls
UI Tests (XCUITest)
- Critical user flows
- Complete workflows
- Screen navigation
- UI interactions
TDD Workflow Steps
Step 1: Write User Stories
As a [role], I want to [action], so that [benefit]
Example:
As a user, I want to search for markets semantically,
so that I can find relevant markets even without exact keywords.
Step 2: Generate Test Cases
For each user story, create comprehensive test cases:
import XCTest
@testable import MyApp
final class MarketSearchServiceTests: XCTestCase {
var sut: MarketSearchService!
var mockAPIClient: MockAPIClient!
override func setUp() {
super.setUp()
mockAPIClient = MockAPIClient()
sut = MarketSearchService(apiClient: mockAPIClient)
}
override func tearDown() {
sut = nil
mockAPIClient = nil
super.tearDown()
}
func test_search_returnsRelevantMarkets() async throws {
// Test implementation
}
func test_search_handlesEmptyQueryGracefully() async throws {
// Test edge case
}
func test_search_fallsBackToLocalSearch_whenNetworkUnavailable() async throws {
// Test fallback behavior
}
func test_search_sortsByRelevanceScore() async throws {
// Test sorting logic
}
}
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.
- 7d ago First seen · 695 lines · 43 tokens per session scan B ab4bcebbf846
swift-tdd-workflow is a skill published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 3,904 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). 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-journey-testing
XML-specified Android UI journey testing, interactive step execution, assertion verification, and JSON outcome reporting.
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.
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…
test-native-extension
Validate a third-party control repo across four automated layers plus one printed manual recipe. Layer 1 asserts native-source structure (Android getName() and iOS +moduleName to manifest nativeModule; @ReactMethod / RCTEXPORTMETHOD to methods; no @ReactModule) plus load/init readiness (ReactPackage public no-arg…