Companion is a self-hosted, multi-tenant hub for managing personal and organizational SKILL.md libraries used by coding agents. It is for organizations that need to store, validate, version, share, install, update, and synchronize agent skills, with optional named companions that have persistent workspaces and chats. The catalogue skills, agents, and instructions are resources managed or used within this workflow.
Borrowing it
Nothing to install: this file belongs to The-Vibe-Company/companion. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/The-Vibe-Company/companion/main/.agents/skills/ios-product-dev/SKILL.mdgit clone --depth 1 https://github.com/The-Vibe-Company/companionWrote 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/the-vibe-company/companion/ios-product-dev)<a href="https://agentmods.dev/skills/the-vibe-company/companion/ios-product-dev"><img src="https://agentmods.dev/badge/skills/the-vibe-company/companion/ios-product-dev/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/the-vibe-company/companion/ios-product-dev"><img src="https://agentmods.dev/badge/skills/the-vibe-company/companion/ios-product-dev.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.01398 |
| Opus 5 | $0.00034 | $0.00699 |
| Sonnet 5 | $0.00013 | $0.00280 |
| Haiku 4.5 | $0.00007 | $0.00140 |
Grade A, and why
ios-product-dev 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 10d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native iOS product development
Use this as the owner skill for a native iOS product change. It covers product intent, platform translation, SwiftUI implementation coordination, and release-quality verification. It does not replace the cross-platform visual owner or the focused SwiftUI and XcodeBuildMCP skills.
Protected invariants
- Read the repository and apps/ios guidance before changing code. Treat those documents, the existing implementation, and the shared API contract as the source of truth.
- Use Swift 6, target iOS 26 or later, and keep the app free of third-party runtime dependencies. Keep models, networking, authentication, secure session state, and polling in CompanionKit; keep SwiftUI presentation and platform integration in the app target.
- Preserve the complete Companion client contract. Use the existing /v1 APIs and shared models; never invent a mobile-only endpoint, send a client-surface discriminator, or hide Skills, Plugins, MCP connections, attachments, routines, triggers, sharing, settings, or other product workflows because the surface is mobile.
- The API persists and reads control-plane intent. The iOS client never contacts Box or Pi directly, never handles Box credentials, and never turns typing, polling, or a Viewer read into a wake action. Sending is the normal wake path; a Viewer remains read-only.
- Do not hand-edit Companion.xcodeproj/project.pbxproj. The project uses file-system-synchronized groups, so ordinary Swift file additions should follow the existing layout.
- Preserve the existing app identities and configuration: Debug uses the local dev bundle and URL scheme, Release uses the production bundle and API URL, and the documented display name, bundle name, team, and App Store record remain unchanged unless the user explicitly changes them.
- Follow the Companion design language: system typography and dynamic colors, flat hairline structure, concise sentence-case copy, explicit status text, and accessible focus and content states. The only glass exception is native iOS 26 system Liquid Glass for navigation and interactive controls. Use system materials for content, provide an opaque fallback for Reduce Transparency, and do not imitate glass with custom shaders, blur stacks, gradients, or third-party components.
- Respect Dynamic Type, VoiceOver, Reduce Motion, Reduce Transparency, sufficient hit targets, keyboard/focus navigation where applicable, and color-independent status communication.
What ships with it
3 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.
- 10d ago First seen · 98 lines · 67 tokens per session scan A 610f89ec1e3e
ios-product-dev is a skill published in the GitHub repository The-Vibe-Company/companion (2,403 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 1,398 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-09-02.
Other skills, from other repositories
animate-expo
Build animations in React Native and Expo, making the decisions in the order that determines whether they feel right — should it animate, which thread it runs on, which properties, spring or timing, how the gesture hands off, how it degrades. Writes the implementation with Reanimated, Gesture Handler, Expo Router and…
leanback-to-compose-tv-migration
Provides instructions and architectural patterns for migrating Android TV applications from legacy Leanback UI Toolkit, Android Views, or Support Fragments to Jetpack Compose for TV (androidx.tv). Use this skill for Leanback to Compose migrations, including browse screen, settings screen, authentication screen, login…
maui-data-binding
Guidance for .NET MAUI XAML and C# data bindings — compiled bindings, INotifyPropertyChanged / ObservableObject, value converters, binding modes, multi-binding, relative bindings, fallbacks, and MVVM best practices. USE FOR: setting up compiled bindings with x:DataType, implementing INotifyPropertyChanged or…
expo-brownfield
Framework (OSS). Integrate Expo and React Native into an existing native iOS or Android app. Use for brownfield, embedding a React Native screen in SwiftUI/UIKit or Kotlin, or AAR/XCFramework packaging. Covers isolated and integrated approaches. For building or distributing a purely native app with EAS, use…
migrate-xml-views-to-jetpack-compose
Provides a structured workflow for migrating an Android XML View to Jetpack Compose. This skill details the step-by-step process, from planning and dependency setup, to theming and layout migration, validation and XML cleanup. Use this skill when you need to migrate an XML View to Jetpack Compose in an Android…
web-haptics
Add haptic feedback to web apps using the web-haptics library. Use when building mobile-facing UIs that need tactile feedback on buttons, toggles, forms, pickers, and other interactive elements.