Borrowing it
Nothing to install: this file belongs to JasonColapietro/ios-app-dev-skills. 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/JasonColapietro/ios-app-dev-skills/main/.claude/commands/ios-native-shell.mdgit clone --depth 1 https://github.com/JasonColapietro/ios-app-dev-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/commands/jasoncolapietro/ios-app-dev-skills/ios-native-shell)<a href="https://agentmods.dev/commands/jasoncolapietro/ios-app-dev-skills/ios-native-shell"><img src="https://agentmods.dev/badge/commands/jasoncolapietro/ios-app-dev-skills/ios-native-shell.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.00014 | $0.00162 |
| Opus 5 | $0.00007 | $0.00081 |
| Sonnet 5 | $0.00003 | $0.00032 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
ios-native-shell 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 7d 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.
What it actually says
/ios-native-shell
Input: $ARGUMENTS - URL, product brief, shell repo path, or native-shell ask.
Use the site-to-ios-app and ios-swiftui-product skills.
Prefer a native shell when a raw web wrapper would be weak:
- native tab/navigation model;
- onboarding and empty states;
- settings with support, privacy, terms, account deletion, and restore when relevant;
- WebView only where the site remains the correct product surface;
- native error, offline, loading, retry, share, and deep-link behavior;
- DEBUG-only demo states for screenshots.
Output an architecture plan, file map, build command, and App Review rationale.
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.
- 7d ago First seen · 22 lines · 14 tokens per session scan A 4e1ebef8ffc1
ios-native-shell is a command published in the GitHub repository JasonColapietro/ios-app-dev-skills (2 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 162 once invoked, about $0.0001 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 commands, from other repositories
apple-polish
Design & keynote craftsmanship review → select issues → fix → TestFlight. Runs the apple-polish skill.
ios-impeccable
The canon is /.claude/docs/reference/design-lane.md — the tier model, the precedence order (owner > aesthetic > detector), the aesthetic-capture protocol, and the shared T1/T2 mechanics are defined THERE, once. This command routes a .swift design request to a tier and executes it with the iOS deltas below. It restates…
mobile
Start mobile design workflow.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.