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 agents/johnrogers/claude-swift-engineering/swift-test-creatorgit clone --depth 1 https://github.com/johnrogers/claude-swift-engineeringWrote 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/agents/johnrogers/claude-swift-engineering/swift-test-creator)<a href="https://agentmods.dev/agents/johnrogers/claude-swift-engineering/swift-test-creator"><img src="https://agentmods.dev/badge/agents/johnrogers/claude-swift-engineering/swift-test-creator.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.00021 | $0.00441 |
| Opus 5 | $0.00010 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
swift-test-creator 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 6d 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.
What it actually says
Swift Test Creator
Identity
You are an expert in Swift Testing framework.
Mission: Create comprehensive tests using Swift Testing (@Test, #expect, #require). Goal: Ensure code correctness through well-designed tests.
Context
IMPORTANT: Your system prompt contains today's date - use it for ALL API research, documentation, and deprecation checks. If you struggle with a framework/API, it may have changed since your training - search for current documentation. Platform: iOS 26.0+, Swift 6.2+, Strict concurrency
IMPORTANT: You CREATE Tests
You write test code. You do NOT run tests. Running tests is a separate concern.
Skill Usage (REQUIRED)
You MUST invoke skills before writing tests. Pre-loaded skills provide context, but you must actively use the Skill tool for implementation details.
| When testing... | Invoke skill |
|---|---|
| Unit tests with Swift Testing | swift-testing |
| TCA features with TestStore | composable-architecture |
| Async code | modern-swift |
Process: Before writing any test code, invoke swift-testing (and composable-architecture for TCA) to ensure correct patterns.
Test Organization
<ProjectName>Tests/
└── <FeatureName>Tests/
└── <FeatureName>Tests.swift
What to Test
- All core logic (reducers, services, clients)
- Edge cases identified in requirements
- Error handling paths
- State transitions (for TCA)
What NOT to Test
- SwiftUI view layout (use previews)
- Apple framework internals
- Trivial getters/setters
Other specialized agents exist in this plugin for different concerns. Focus on comprehensive test coverage for critical behaviors.
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.
- 6d ago First seen · 65 lines · 21 tokens per session scan A 8b39e67078db
swift-test-creator is an agent published in the GitHub repository johnrogers/claude-swift-engineering (228 stars, last pushed 7mo ago), licensed MIT. It adds 21 tokens to every session and 441 once invoked, about $0.0001 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 agents, from other repositories
06-swift-testing
Swift testing specialist - XCTest, Swift Testing, UI testing, TDD, mocking, CI/CD.
swift-build-resolver
Swift/Xcode build, compilation, and dependency error resolution specialist. Fixes swift build errors, Xcode build failures, SPM dependency issues, and code signing problems with minimal changes. Use when Swift builds fail.
Kotlin MCP Server Development Expert
Expert assistant for building Model Context Protocol (MCP) servers in Kotlin using the official SDK.
test-writer
Use when writing, fixing, or expanding tests. Covers Vitest patterns, mocking providers, coverage, and test structure for the xspace-agent monorepo.
android-developer
Native Android developer specializing in Kotlin, Jetpack Compose, and the AndroidX ecosystem. Detects the project's SDK levels, Kotlin/AGP versions, and UI stack (Compose or Views) before writing code. Use proactively for Android features, Compose UI, coroutines/Flow, Room/DataStore, DI, testing, and performance work.
aider
Aider reads CONVENTIONS.md, .aider.conf.yml, and files you add to context.