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 Desquared/agents-rules-skills --skill ios-swift-api-design-reviewergit clone --depth 1 https://github.com/Desquared/agents-rules-skillsWrote 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/desquared/agents-rules-skills/ios-swift-api-design-reviewer)<a href="https://agentmods.dev/skills/desquared/agents-rules-skills/ios-swift-api-design-reviewer"><img src="https://agentmods.dev/badge/skills/desquared/agents-rules-skills/ios-swift-api-design-reviewer/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/skills/desquared/agents-rules-skills/ios-swift-api-design-reviewer"><img src="https://agentmods.dev/badge/skills/desquared/agents-rules-skills/ios-swift-api-design-reviewer.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.00064 | $0.01342 |
| Opus 5 | $0.00032 | $0.00671 |
| Sonnet 5 | $0.00013 | $0.00268 |
| Haiku 4.5 | $0.00006 | $0.00134 |
Grade A, and why
ios-swift-api-design-reviewer 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 11d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift API Design Review
What “good” looks like
- Prioritize clarity at the call site, even if the declaration becomes a bit longer.
- Follow established standard library conventions so your API “feels Swift”.
- Prefer precise words over generic ones (
data,info,manager,handler,util).
Naming Rules (Types, Properties, Methods)
- Clear at point of use, not at declaration.
- Omit needless words, but do not remove words that carry meaning.
- lowerCamelCase: functions, methods, properties, enum cases.
- UpperCamelCase: types, protocols.
- Avoid “noise” suffixes like
String,Array,Dataunless they add meaning.
Boolean naming
- Prefer predicates:
is,has,can,should,did. - Match the natural reading of the call site.
- ✅
if user.isEligible { … } - ✅
if cache.hasValue(forKey: k) { … }
- ✅
Verbs and mutability
- Mutating methods are verbs:
sort(),append(_),removeAll(). - Non-mutating counterparts use “-ed”:
sorted(),appending(_),removingAll()when appropriate.
Common Issues (with better fixes)
| Issue | Better Fix |
|---|---|
var visible |
var isVisible |
func get() |
Use a precise verb or a noun that reads well at the call site: func userName(), func loadUserName(), func fetchUserName() |
var nameString |
var name |
func add(item: x, to: y) |
func add(_ item: Item, to collection: Collection) |
func doStuff() |
Name the domain action: func refresh(), func rebuildIndex(), func startSession() |
func handle(_ x: …) |
Be specific: func handleDeepLink(_:) or func route(_:) |
Parameter & Label Design (call-site first)
- The first argument label should be omitted when it forms a natural phrase:
- ✅
add(_ item:to:) - ✅
contains(_:)
- ✅
- Use labels to clarify roles, units, and semantics:
- ✅
move(from:to:) - ✅
setDeadline(_:, for:) - ✅
resize(to:)(size),resize(by:)(scale factor)
- ✅
- Keep default parameters last when it improves scanning and discoverability.
- Closure parameters are usually last, but:
- If there are multiple closures, label them clearly.
- If a closure is configuration rather than action, it may be clearer earlier.
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.
- 11d ago First seen · 127 lines · 64 tokens per session scan A 0dae78ab446b
ios-swift-api-design-reviewer is a skill published in the GitHub repository Desquared/agents-rules-skills (4 stars, last pushed 28d ago), licensed MIT. It adds 64 tokens to every session and 1,342 once invoked, about $0.0003 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-31.
Other skills, from other repositories
axiom-audit-codable
Use when the user mentions Codable review, JSON encoding/decoding issues, data serialization audit, or modernizing legacy code.
axiom-swift-simplifier
Use when the user wants to simplify Swift code, reduce boilerplate, or make Swift more readable and idiomatic without changing behavior.
kotlin-concurrency-and-flow
Use when writing or reviewing Kotlin coroutine scope ownership, raw Thread or Executor work, init launches, non-suspending launch APIs, runBlocking, cancellation, StateFlow, SharedFlow, Channel, stateIn, SharingStarted, state updates, or one-shot events.
kotlin-api-design
Use when designing or reviewing Kotlin function ownership, member or extension functions, factories, single-field domain types, value classes, data classes, Kotlin Multiplatform expect/actual declarations, or platform service boundaries.
coding-best-practices
Reviews Swift/iOS code for adherence to modern Swift idioms, Apple platform best practices, architecture patterns, and code quality standards. Use when user mentions best practices, code review, clean code, refactoring, or wants to improve code quality.
swift-concurrency-review
Review Swift 6 strict-concurrency and SwiftUI code for idiom and build-breaking issues - non-Sendable across actor boundaries, @MainActor witness vs nonisolated protocol requirements, Combine/ObservableObject usage, force-unwraps, #Predicate macro limits, the 6.3.x Binding IRGen crash, missing #if os() guards, and…