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.
git clone --depth 1 https://github.com/GktuOktay/ai-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/rules/gktuoktay/ai-skills/onboarding)<a href="https://agentmods.dev/rules/gktuoktay/ai-skills/onboarding"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/onboarding/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/rules/gktuoktay/ai-skills/onboarding"><img src="https://agentmods.dev/badge/rules/gktuoktay/ai-skills/onboarding.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00912 |
| Opus 5 | $0.00000 | $0.00456 |
| Sonnet 5 | $0.00000 | $0.00182 |
| Haiku 4.5 | $0.00000 | $0.00091 |
Grade A, and why
onboarding 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 8d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Onboarding Flow Design
Creating an effective onboarding experience is critical for user retention, feature discovery, and product success. A well-designed onboarding flow guides users to their "Aha!" moment as quickly as possible.
1. First-Time User Experience (FTUE) Patterns
FTUE sets the tone for the user's relationship with the product. Key patterns include:
- Welcome Screens: A warm greeting setting expectations and showcasing core value propositions.
- Product Tours: Guided walkthroughs of the interface.
- Progressive Profiling: Asking for user data incrementally rather than upfront.
- Sandbox Environments: Providing a safe, pre-populated space for users to experiment.
- Checklists: Gamified lists of tasks to guide initial actions.
2. Progressive Disclosure
Do not overwhelm the user. Reveal information and features only when they are needed.
- Contextual Tooltips: Show hints when a user interacts with or hovers over a new feature.
- Just-in-Time Permissions: Request permissions (camera, location, notifications) exactly when the feature requiring them is used, not immediately upon launch.
- Advanced Features: Hide complex settings behind "Advanced" toggles or menus until the user demonstrates basic proficiency.
3. Empty States
Empty states (e.g., a newly created inbox or an empty dashboard) are prime onboarding opportunities.
- Educate: Explain what will appear in this space.
- Direct Action: Provide clear primary CTAs (e.g., "Create your first project").
- Provide Templates: Offer starter content instead of starting from absolute zero.
4. Mobile App Permission Requests (iOS/Android Best Practices)
Mobile OS permissions can make or break an app. Rejection rates are high if handled poorly.
- Prime the User: Before showing the system dialogue, show a custom pre-prompt explaining why the permission is needed and how it benefits the user.
- Delay Requests: Never ask for push notifications or location access immediately after installation. Wait until the user performs an action that justifies it.
- Graceful Degradation: If permission is denied, ensure the app still functions in a limited capacity and provide a path to enable it later in settings.
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.
- 8d ago First seen · 68 lines · 912 tokens per session scan A 0a6ef590c626
onboarding is a cursor rule published in the GitHub repository GktuOktay/ai-skills (2 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 912 tokens. 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 cursor rules, from other repositories
motion-designer
Act as a Senior Motion Designer to specify and ship purposeful UI animation — micro-interactions, transitions, scroll-driven sequences, p...
ui-components
USE WHEN: Building UI components, structuring layouts, and applying styles using Tailwind CSS.
figma-translator
Translate any technical specification into five precise, self-contained Figma Make prompts ready to paste and generate.
canonical__hhadcn-ui
Cursor rule "canonical__hhadcn-ui" from Bilal140202/the-lord-of-the-skills, covering shadcn/ui best practices, installation, initial setup, initialize shadcn/ui in your project and add components as needed.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.