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 skills add Kevin-Liu-01/Agent-Machines --skill app-onboarding-questionnairegit clone --depth 1 https://github.com/Kevin-Liu-01/Agent-MachinesWrote 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/kevin-liu-01/agent-machines/app-onboarding-questionnaire)<a href="https://agentmods.dev/skills/kevin-liu-01/agent-machines/app-onboarding-questionnaire"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/app-onboarding-questionnaire/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/kevin-liu-01/agent-machines/app-onboarding-questionnaire"><img src="https://agentmods.dev/badge/skills/kevin-liu-01/agent-machines/app-onboarding-questionnaire.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 56 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00122 | $0.01954 |
| Opus 5 | $0.00061 | $0.00977 |
| Sonnet 5 | $0.00024 | $0.00391 |
| Haiku 4.5 | $0.00012 | $0.00195 |
Grade A, and why
app-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 12d 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 — 167 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 memory first.
RECALL (Always Do This First)
Before doing ANY codebase analysis, check the Claude Code memory system for all previously saved state for this app. The skill saves progress at each phase, so the user can resume from wherever they left off.
Check memory 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 the CLAUDE.md and Codebase
Look at:
- CLAUDE.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.
- 12d ago First seen · 167 lines · 122 tokens per session scan A 4dc4a62fd631
app-onboarding-questionnaire is a skill published in the GitHub repository Kevin-Liu-01/Agent-Machines (29 stars, last pushed today), licensed MIT. It adds 122 tokens to every session and 1,954 once invoked, about $0.0006 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
21st-ui
Find, install, and generate UI with 21st.dev. Use when the user asks for a UI component (pricing table, hero, navbar, dashboard, form, etc.), wants design inspiration, needs a brand logo as an SVG component, or wants to generate new UI from a prompt.
harness-design-fuzzing
Reference vocabulary for designing instrumented harnesses that drive vulnerability discovery — design classes (trigger-driven vs coverage-driven), tiered scope (T1 isolated function / T2 multi-component / T3 full build), systematic input exploration, the two-coverage distinction (fuzzer-feedback vs audit)…
workspace-builder
Build ServiceNow App Engine Studio applications — sysscope creation, scoped tables, sysawworkspace with lists/forms, the sysux record chain behind UI Builder workspaces, data brokers, and application export readiness checks. Never create a UI Builder page by inserting a sysuxpage row.
ui-builder-patterns
Build ServiceNow UI Builder / Next Experience pages — macroponents, GraphQL/script data brokers, client state parameters, event handlers (NOWRECORDLIST etc.), and now-record-list/form component configuration.
remotion
Create editable AI video projects with Remotion and React, then preview and render them to MP4. Use for vertical short videos, product demos, story-driven animations, HUD/tech visuals, feed ads, tutorial videos, subtitles, voiceover, sound effects, and code-based video iteration.
widget-coherence
Build Service Portal widgets (spwidget) with synchronized server/client/HTML — data. initialization, ng-click + controller method matching, c.server.get action handlers, and Angular directive usage.