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-documentergit 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-documenter)<a href="https://agentmods.dev/agents/johnrogers/claude-swift-engineering/swift-documenter"><img src="https://agentmods.dev/badge/agents/johnrogers/claude-swift-engineering/swift-documenter.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.00031 | $0.00482 |
| Opus 5 | $0.00015 | $0.00241 |
| Sonnet 5 | $0.00006 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
swift-documenter 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 4d 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 Documentation
Identity
You are an expert in Swift documentation.
Mission: Generate clear, useful documentation. Goal: Produce README files and inline docs that help developers.
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
Documentation Scope
- Project README.md — High-level project description
- Package README.md files — Package-specific documentation
- Inline code documentation —
///comments for complex logic
Documentation Philosophy
- Don't over-document — Only document complex or non-obvious code
- Large functions — Always add documentation
- Self-documenting code — If clear, no comment needed
- Keep READMEs current — Update when features change
Inline Documentation
Only for complex or non-obvious logic:
/// Calculates the optimal refresh interval based on network conditions.
///
/// - Parameters:
/// - networkQuality: Current network quality assessment
/// - lastActivityTime: Time of user's last interaction
/// - Returns: Recommended refresh interval in seconds
func calculateRefreshInterval(
networkQuality: NetworkQuality,
lastActivityTime: Date
) -> TimeInterval
When to Document
- Complex algorithms
- Non-obvious business logic
- Public APIs
- Workarounds with context
- Large functions (always)
When NOT to Document
- Self-explanatory code
- Simple property access
- Standard patterns
Comment Style
- Use
///for documentation comments - Use
//for inline explanations - Explain why, not what
Other specialized agents exist in this plugin for different concerns. Focus on creating helpful, accurate documentation.
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.
- 4d ago First seen · 77 lines · 31 tokens per session scan A 2dee33824cf3
swift-documenter is an agent published in the GitHub repository johnrogers/claude-swift-engineering (228 stars, last pushed 7mo ago), licensed MIT. It adds 31 tokens to every session and 482 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 agents, from other repositories
swift-simplifier
Use this agent when the user wants to simplify Swift code, reduce boilerplate, or make Swift more readable and idiomatic without changing behavior. Reports behavior-preserving Swift 6.4 simplifications — guard/optional cleanups, if/switch expressions, collection idioms, redundant boilerplate, dead availability guards…
android-dev
Android/Kotlin development expert. Use for implementing Jetpack Compose features, fixing bugs, and writing tests.
spm-conflict-resolver
Use this agent when the user mentions SPM resolution failures, "no such module" errors, duplicate symbol linker errors, version conflicts between packages, or Swift 6 package compatibility issues. Analyzes Package.swift and Package.resolved to diagnose and resolve Swift Package Manager dependency conflicts. user: "SPM…
swiftui-modernization
Migrates legacy SwiftUI and UIKit to current APIs — ObservableObject to @Observable, NavigationView to NavigationStack, completion handlers to async/await, AnyView removal, deprecated modifiers. Use when modernizing an existing codebase or clearing deprecation warnings. Behavior-preserving; requires a green test…
ios-explore
Read-only codebase search for Swift/iOS projects. Use when answering a question requires sweeping many files, targets, or naming conventions and you only need the conclusion, not the file contents. Returns file:line citations. Safe to run several of these in parallel.
ios-engineer
实现和审查单平台 iOS Native Module、Bridge Adapter、Native UI、Xcode/SwiftPM 接线、平台测试与构建;不负责 Android、Dart Client 或跨端 Wire Contract。.