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/moasq/ios-dev-agent/onboarding-questionnairenpx skills add moasq/ios-dev-agent --skill onboarding-questionnairegit clone --depth 1 https://github.com/moasq/ios-dev-agentWrote 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/moasq/ios-dev-agent/onboarding-questionnaire)<a href="https://agentmods.dev/skills/moasq/ios-dev-agent/onboarding-questionnaire"><img src="https://agentmods.dev/badge/skills/moasq/ios-dev-agent/onboarding-questionnaire.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.00070 | $0.04945 |
| Opus 5 | $0.00035 | $0.02472 |
| Sonnet 5 | $0.00014 | $0.00989 |
| Haiku 4.5 | $0.00007 | $0.00494 |
Grade A, and why
onboarding-questionnaire 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 6d 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.
This is a copy
92% identical to app-onboarding-questionnaire — 50 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert mobile app onboarding designer and conversion strategist. Your job is to help the user design and implement a high-converting onboarding flow for their app — the kind used by top subscription apps like Mob, Headspace, Duolingo, and Noom.
This is a multi-phase process. Follow each phase in order, but always check local handoff state first.
RECALL (Always Do This First)
Before doing any codebase analysis, check local handoff files and recent git changes for previously saved state for this app. The skill should save progress at each phase, so the user can resume from wherever they left off.
Check .agents/handoff/, relevant feature files, and recent git diff for each of these (in order):
- App profile — what the app does, target audience, platform/framework, core features
- User transformation — the before/after state the app creates for its users
- Onboarding blueprint — the confirmed screen sequence with objectives
- Screen content — headlines, options, copy for each screen
- Implementation progress — which screens have been built, file paths
Present a status summary to the user showing what's saved and what phase they're at. For example:
Here's where we left off:
✅ App profile: Fitness tracking app (SwiftUI)
✅ User transformation: "Confused about what to eat" → "Confident meal planner"
✅ Blueprint: 11-screen flow confirmed
⏳ Screen content: 6 of 11 screens drafted
◻️ Implementation: not started
Ready to continue drafting screen 7, or would you like to change anything?
If NO state is found in memory at all: → Proceed to Phase 1: App Discovery.
PHASE 1: APP DISCOVERY
Analyze the user's app codebase to understand what it does and who it's for.
Step 1: Read AGENTS.md and the Codebase
Look at:
- AGENTS.md, README, any marketing copy or App Store metadata
- UI files, views, screens, components — what can the user DO in this app?
- Models and data structures — what domain does this operate in?
- Onboarding flows (if any exist already)
- Subscription/paywall code (if any)
- Core user-facing features — identify the ONE thing a user would do in their first session
- Permission usage — check Info.plist (iOS), AndroidManifest.xml, or equivalent for permissions the app requests (notifications, location, camera, health data, contacts, etc.)
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.
- 6d ago First seen · 420 lines · 70 tokens per session scan A 90a903dd062e
onboarding-questionnaire is a skill published in the GitHub repository moasq/ios-dev-agent (4 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 4,945 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to app-onboarding-questionnaire, differing in 50 lines, and is treated as a copy.
Other skills, from other repositories
orca-emulator-android
Control an Android emulator / device from inside Orca using the orca CLI. Use for listing/booting AVDs, taps, swipes, typing, hardware buttons (incl. Back and Recents), rotation, app install/launch, runtime permissions, the accessibility tree, and logcat — driving a real adb-connected device or emulator.…
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
winapp-maui
Package and sign .NET MAUI Windows apps with winapp, resolving the resizetizer manifest dependency. Use when packaging or signing a .NET MAUI Windows app, building a MAUI MSIX or signed unpackaged build in CI, or fixing 'manifest contains unresolved placeholders ($placeholder$)' errors from winapp package.
apple-search-ads
When the user wants to set up, optimize, or scale Apple Search Ads (ASA) campaigns — including keyword bidding, match types, campaign structure, Creative Product Sets, CPP routing, and ROAS optimization. Use when the user mentions "Apple Search Ads", "ASA", "Search Ads", "Search tab ads", "Today tab ads", "CPT"…
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.