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 skills/getstream/agent-skills/stream-swiftnpx skills add GetStream/agent-skills --skill stream-swiftgit clone --depth 1 https://github.com/GetStream/agent-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/getstream/agent-skills/stream-swift)<a href="https://agentmods.dev/skills/getstream/agent-skills/stream-swift"><img src="https://agentmods.dev/badge/skills/getstream/agent-skills/stream-swift.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.00080 | $0.03809 |
| Opus 5 | $0.00040 | $0.01904 |
| Sonnet 5 | $0.00016 | $0.00762 |
| Haiku 4.5 | $0.00008 | $0.00381 |
Grade A, and why
stream-swift 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream Swift - docs orchestrator for iOS
This skill is small on purpose. It does not bundle SDK reference dumps - the official iOS docs are the source of truth and they cover the entire surface (Chat, Video, Feeds; SwiftUI and UIKit; polls, drafts, voice, AI, push, screen share, CallKit, SIP, transcriptions, moderation, and more).
Your job is to orchestrate: classify the request, point to the exact docs page, fetch it live, and apply it inside the user's project - while obeying the curated rules and pitfalls that the docs do not shout about.
Rules (read once per session): RULES.md - non-negotiable rules + iOS pitfalls. Read before writing any code.
The docs convention (the core mechanism)
Every Stream docs page has a Markdown twin that coding agents can read directly: take the page URL, drop the trailing /, add .md.
https://getstream.io/chat/docs/sdk/ios/basics/integration/ -> https://getstream.io/chat/docs/sdk/ios/basics/integration.md
Always fetch the .md variant - it is clean Markdown with verbatim code, no page chrome.
Per-product index pages list every doc page with its .md URL. Fetch these to discover or confirm a page:
| Product | Live index (always current) | Page URL shape |
|---|---|---|
| Chat (iOS SDK: UI + State Layer) | https://getstream.io/cli/docs/chat-sdk-ios.md |
https://getstream.io/chat/docs/sdk/ios/...md |
| Chat (low-level client API reference) | https://getstream.io/cli/docs/chat-ios-swift.md |
https://getstream.io/chat/docs/ios-swift/...md |
| Video | https://getstream.io/cli/docs/video-ios.md |
https://getstream.io/video/docs/ios/...md |
| Feeds | https://getstream.io/cli/docs/activity-feeds-ios.md |
https://getstream.io/activity-feeds/docs/ios/...md |
URL grounding: only fetch a page URL that you got from docs-map.md or from a live index fetch in this conversation. Do not invent doc paths from memory - many look guessable but are wrong. If a page is not in the map, fetch the live index and pick from it.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 125 lines · 80 tokens per session scan A 9a708f9c1803
stream-swift is a skill published in the GitHub repository GetStream/agent-skills (18 stars, last pushed 3d ago), licensed Apache-2.0. It adds 80 tokens to every session and 3,809 once invoked, about $0.0004 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 skills, from other repositories
swift
Design, implement, and review Swift APIs and Apple-platform code. Use when working on .swift files, Swift types, Foundation or AVFoundation APIs, DispatchQueue, async/await, Task, actors, MainActor, thread-affine state, or Swift-backed React Native Nitro Module implementations.
kotlin
Design, implement, and review Kotlin and Android APIs. Use when working on .kt files, Kotlin nullability, sealed classes/interfaces, coroutines, Android threading, Java interop, or Kotlin-backed React Native Nitro Module implementations.
app-implement-feature
Guide for implementing features in baguette — a Swift CLI + WebSocket server that drives iOS simulators via private SimulatorKit. Use this skill when: (1) Adding a new gesture, button, keyboard surface, stream format, or device-chrome behaviour (anything that lands across Domain / Infrastructure / App +…
building-ui
Complete guide for building beautiful apps with Expo Router. Covers fundamentals, styling, components, navigation, animations, patterns, and native tabs.
use-dom
Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.
ii-app
Use this skill when you need to initialize or restart local web and mobile app projects through the bundled Rust ii-app CLI instead of calling MCP tools.