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 commands/okminlee/everything-claude-code-ios/swift-tddgit 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/commands/okminlee/everything-claude-code-ios/swift-tdd)<a href="https://agentmods.dev/commands/okminlee/everything-claude-code-ios/swift-tdd"><img src="https://agentmods.dev/badge/commands/okminlee/everything-claude-code-ios/swift-tdd.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 | $0.00033 | $0.03079 |
| Opus 5 | $0.00016 | $0.01540 |
| Sonnet 5 | $0.00007 | $0.00616 |
| Haiku 4.5 | $0.00003 | $0.00308 |
Grade A, and why
swift-tdd 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 5d 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 — 469 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift TDD Command
This command invokes the swift-tdd-guide agent to enforce test-driven development methodology for iOS projects.
What This Command Does
- Define Protocols - Establish contracts and interfaces first
- Write Tests First - Create failing tests using Swift Testing (RED)
- Implement Minimal Code - Write just enough to pass (GREEN)
- Refactor - Improve code while keeping tests green (REFACTOR)
- Verify Coverage - Ensure 80%+ test coverage
When to Use
Use /swift-tdd when:
- Implementing new iOS features
- Adding new ViewModels, UseCases, or Repositories
- Fixing bugs (write test that reproduces bug first)
- Refactoring existing Swift code
- Building critical business logic
How It Works
The swift-tdd-guide agent will:
- Define protocols for dependencies and contracts
- Write tests that will FAIL (because code doesn't exist yet)
- Run tests and verify they fail for the right reason
- Write minimal implementation to make tests pass
- Run tests and verify they pass
- Refactor code while keeping tests green
- Check coverage and add more tests if below 80%
TDD Cycle
RED → GREEN → REFACTOR → REPEAT
RED: Write a failing test using #expect
GREEN: Write minimal code to pass
REFACTOR: Improve code, keep tests passing
REPEAT: Next feature/scenario
Example Usage
User: /swift-tdd I need a use case to calculate market liquidity score
Agent (swift-tdd-guide):
# TDD Session: Market Liquidity Score Calculator
## Step 1: Define Protocol (SCAFFOLD)
```swift
// Domain/UseCases/LiquidityCalculator.swift
import Foundation
struct MarketData: Sendable {
let totalVolume: Double
let bidAskSpread: Double
let activeTraders: Int
let lastTradeTime: Date
}
protocol LiquidityCalculating: Sendable {
func calculateScore(for market: MarketData) -> Double
}
// Placeholder implementation
struct LiquidityCalculator: LiquidityCalculating {
func calculateScore(for market: MarketData) -> Double {
fatalError("Not implemented")
}
}
Step 2: Write Failing Test (RED)
// Tests/Domain/LiquidityCalculatorTests.swift
import Testing
@testable import MyApp
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.
- 5d ago First seen · 469 lines · 33 tokens per session scan A 6eb85a349f4d
swift-tdd is a command published in the GitHub repository OkminLee/everything-claude-code-ios (58 stars, last pushed 5mo ago), licensed MIT. It adds 33 tokens to every session and 3,079 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 commands, from other repositories
mobile-tdd
Mobile TDD workflow. Write tests first, implement, refactor. 80%+ coverage required.
tdd
XCTest-driven workflow for new features and refactors.
pm-auto-design2dev
設計レビューから実装完了まで完全自動化(設計レビュー→作業計画→TDD実装).
speckit.tdd.plan
Derive the feature's test list by delegating to zfa tdd plan (deterministic engine); falls back to LLM-guided derivation only when zfa is unavailable.
compose-test
Run Compose UI tests with Espresso. Verify critical user flows.
gentle-sdd-apply
Implement SDD tasks — writes code following specs and design.