Borrowing it
Nothing to install: this file belongs to tellahq/opensession. 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/tellahq/opensession/main/.agents/skills/apple-mobile/SKILL.mdgit clone --depth 1 https://github.com/tellahq/opensessionWrote 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/tellahq/opensession/apple-mobile)<a href="https://agentmods.dev/skills/tellahq/opensession/apple-mobile"><img src="https://agentmods.dev/badge/skills/tellahq/opensession/apple-mobile.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.1 | $0.00033 | $0.00516 |
| Opus 5 | $0.00016 | $0.00258 |
| Sonnet 5 | $0.00007 | $0.00103 |
| Haiku 4.5 | $0.00003 | $0.00052 |
Grade A, and why
apple-mobile 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 3d 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apple mobile workflow
Use apple_mobile_doctor and apple_mobile_inspect_project before any build.
Safety rules
- Never paste or print an App Store Connect private key, Apple password, certificate private key, or provisioning secret.
- Treat xtool as a development-build backend only. Do not claim its current development profiles are ad-hoc or App Store profiles.
- Never release from a dirty worktree or an unapproved branch.
- Never call
apple_release_executein the same response that creates a plan. Show the full project path, plan ID, commit, version/build, destination, effects, and any IPA filename and SHA-256. A signed-in allowed person must approve that exact pending plan later in Settings → Integrations → Apple mobile. - The execute confirmation must be the full commit SHA from the reviewed plan.
- TestFlight upload is not App Review submission or public release. This integration deliberately exposes neither action.
- Do not revoke certificates.
Development
- Run
apple_mobile_doctor. - Run
apple_mobile_inspect_project. - Run
apple_mobile_testwhere the package has host-portable tests. - Use
apple_mobile_build_unsignedfor a non-signing build. - Inspect generated IPAs with
apple_mobile_inspect_ipa.
Ad-hoc or TestFlight
- Run
apple_release_doctorand inspect the project. - Create a plan using
apple_release_plan_adhoc,apple_release_plan_testflight, orapple_release_plan_upload. - Present the full project path, plan ID, commit, effects, and any IPA filename and SHA-256, then stop. The planning response cannot authorize execution.
- Ask a signed-in allowed person to approve the exact pending plan in Settings → Integrations → Apple mobile.
- In a later turn, call
apple_release_executewith the plan ID and full planned commit SHA. The server consumes the one-time approval grant. - Report the output artifact SHA-256 or upload result. Do not imply Apple processing has completed unless separately verified.
Repository contract
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.
- 3d ago First seen · 40 lines · 33 tokens per session scan A f7f5e798a750
apple-mobile is a skill published in the GitHub repository tellahq/opensession (355 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 516 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-09-03.
Other skills, from other repositories
wear-compose-m3
Expert guidance for working with Wear OS Compose Material3. Use this skill when creating, updating, or migrating Wear OS projects. This includes the androidx.wear.compose.material3, androidx.wear.compose.foundation, and androidx.wear.compose.navigation3 libraries. Also working with core components such as AppScaffold…
kotlin-specialist
Provides idiomatic Kotlin implementation patterns including coroutine concurrency, Flow stream handling, multiplatform architecture, Compose UI construction, Ktor server setup, and type-safe DSL design. Use when building Kotlin applications requiring coroutines, multiplatform development, or Android with Compose.…
build-android-binary
Compile a PAM control's Android Kotlin module into the runtime-loadable DEX for a .ppmplugin. Creates a staged Gradle build with the pinned wrapper and react-android compile dependency, verifies manifest/module/package alignment and runtime-loading constraints, builds the release AAR, then runs d8 --min-api 24. Writes…
swiftui-dev
Use this skill for SwiftUI development, architecture, structure, performance, and Apple native app profiling. It combines.
android-navigation-3
Install and migrate to Jetpack Navigation 3. Use when implementing Navigation 3 patterns including NavDisplay, NavKey routes, deep links, multiple backstacks, scenes (dialogs, bottom sheets), or migrating from Navigation 2.
mobiai-kmp
Use when working on a Kotlin Multiplatform project — shared code, expect/actual declarations, platform-specific implementations, building and testing.