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 ComeOnOliver/skillshub --skill axiom-swift-concurrencygit clone --depth 1 https://github.com/ComeOnOliver/skillshubWrote 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/comeonoliver/skillshub/axiom-swift-concurrency)<a href="https://agentmods.dev/skills/comeonoliver/skillshub/axiom-swift-concurrency"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-swift-concurrency/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/comeonoliver/skillshub/axiom-swift-concurrency"><img src="https://agentmods.dev/badge/skills/comeonoliver/skillshub/axiom-swift-concurrency.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.00089 | $0.06270 |
| Opus 5 | $0.00044 | $0.03135 |
| Sonnet 5 | $0.00018 | $0.01254 |
| Haiku 4.5 | $0.00009 | $0.00627 |
Grade A, and why
axiom-swift-concurrency scanned grade A 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
return try context.fetch(descriptor) How it starts
The opening of the file, as written. The whole thing — 955 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift 6 Concurrency Guide
Purpose: Progressive journey from single-threaded to concurrent Swift code
Swift Version: Swift 6.0+, Swift 6.2+ for @concurrent
iOS Version: iOS 17+ (iOS 18.2+ for @concurrent)
Xcode: Xcode 16+ (Xcode 16.2+ for @concurrent)
Context: WWDC 2025-268 "Embracing Swift concurrency" - approachable path to data-race safety
When to Use This Skill
✅ Use this skill when:
- Starting a new project and deciding concurrency strategy
- Debugging Swift 6 concurrency errors (actor isolation, data races, Sendable warnings)
- Deciding when to introduce async/await vs concurrency
- Implementing
@MainActorclasses or async functions - Converting delegate callbacks to async-safe patterns
- Deciding between
@MainActor,nonisolated,@concurrent, or actor isolation - Resolving "Sending 'self' risks causing data races" errors
- Making types conform to
Sendable - Offloading CPU-intensive work to background threads
- UI feels unresponsive and profiling shows main thread bottleneck
❌ Do NOT use this skill for:
- General Swift syntax (use Swift documentation)
- SwiftUI-specific patterns (use
axiom-swiftui-debuggingoraxiom-swiftui-performance) - API-specific patterns (use API documentation)
Core Philosophy: Start Single-Threaded
Apple's Guidance (WWDC 2025-268): "Your apps should start by running all of their code on the main thread, and you can get really far with single-threaded code."
The Progressive Journey
Single-Threaded → Asynchronous → Concurrent → Actors
↓ ↓ ↓ ↓
Start here Hide latency Background Move data
(network) CPU work off main
When to advance:
- Stay single-threaded if UI is responsive and operations are fast
- Add async/await when high-latency operations (network, file I/O) block UI
- Add concurrency when CPU-intensive work (image processing, parsing) freezes UI
- Add actors when too much main actor code causes contention
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.
- 8d ago First seen · 955 lines · 89 tokens per session scan A eb8bb4946bfc
axiom-swift-concurrency is a skill published in the GitHub repository ComeOnOliver/skillshub (63 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 6,270 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
android-clean-architecture
Clean Architecture patterns for Android and Kotlin Multiplatform projects — module structure, dependency rules, UseCases, Repositories, and data layer patterns.
compose-multiplatform-patterns
Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.
swiftui-patterns
SwiftUI architecture patterns, state management with @Observable, view composition, navigation, performance optimization, and modern iOS/macOS UI best practices.
swift-development
You MUST activate this skill when working on Swift projects.
ios-development
Comprehensive iOS app development skill. Use this skill for ANY iOS-related task: writing Swift/SwiftUI/UIKit code, architecting apps, debugging crashes, setting up navigation, networking, data persistence, animations, performance optimization, App Store submission, Xcode configuration. Trigger when user mentions…
kotlin-expert
Expert-level Kotlin development, Android, coroutines, and multiplatform. Use when the user mentions Android, coroutines, multiplatform, or JVM, or when the task involves Kotlin Fundamentals, Android Development, Kotlin Multiplatform, or Kotlin Style.