Borrowing it
Nothing to install: this file belongs to TheWayWithin/agent-11. 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/TheWayWithin/agent-11/main/.claude/skills/saas-onboarding/SKILL.mdgit clone --depth 1 https://github.com/TheWayWithin/agent-11Wrote 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/thewaywithin/agent-11/saas-onboarding)<a href="https://agentmods.dev/skills/thewaywithin/agent-11/saas-onboarding"><img src="https://agentmods.dev/badge/skills/thewaywithin/agent-11/saas-onboarding.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00004 | $0.02942 |
| Opus 5 | $0.00002 | $0.01471 |
| Sonnet 5 | $0.00001 | $0.00588 |
| Haiku 4.5 | $0.00000 | $0.00294 |
Grade A, and why
saas-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 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 — 437 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS User Onboarding
Capability
Implement effective user onboarding flows that drive activation and reduce churn. Covers setup wizards, progress checklists, contextual tooltips, and tracking of key activation milestones. Focus on getting users to their "aha moment" quickly.
Use Cases
- Multi-step setup wizard after signup
- Onboarding checklist with progress tracking
- Contextual tooltips and feature tours
- Activation milestone tracking
- Re-engagement for incomplete onboarding
- Team member onboarding variations
Patterns
Onboarding State Machine
When to use: Track user progress through onboarding steps
Implementation: Persist onboarding state with completed steps and progress.
// Onboarding state schema
const onboardingStates = pgTable('onboarding_states', {
id: uuid('id').primaryKey().defaultRandom(),
userId: uuid('user_id').references(() => users.id).unique(),
currentStep: text('current_step').notNull().default('welcome'),
completedSteps: jsonb('completed_steps').$type<string[]>().default([]),
stepData: jsonb('step_data').$type<Record<string, unknown>>().default({}),
startedAt: timestamp('started_at').defaultNow(),
completedAt: timestamp('completed_at'),
skippedAt: timestamp('skipped_at')
});
// Onboarding steps definition
const ONBOARDING_STEPS = [
{ id: 'welcome', title: 'Welcome', required: true },
{ id: 'profile', title: 'Complete Profile', required: true },
{ id: 'create_project', title: 'Create First Project', required: true },
{ id: 'invite_team', title: 'Invite Team Members', required: false },
{ id: 'connect_integration', title: 'Connect Integration', required: false },
{ id: 'explore_features', title: 'Explore Features', required: false }
] as const;
// Get onboarding status
async function getOnboardingStatus(userId: string) {
const state = await db.query.onboardingStates.findFirst({
where: eq(onboardingStates.userId, userId)
});
if (!state) {
// Initialize onboarding
const [newState] = await db.insert(onboardingStates)
.values({ userId })
.returning();
return formatOnboardingStatus(newState);
}
return formatOnboardingStatus(state);
}
function formatOnboardingStatus(state: OnboardingState) {
const totalRequired = ONBOARDING_STEPS.filter(s => s.required).length;
const completedRequired = state.completedSteps
.filter(stepId => ONBOARDING_STEPS.find(s => s.id === stepId)?.required)
.length;
return {
currentStep: state.currentStep,
completedSteps: state.completedSteps,
progress: Math.round((completedRequired / totalRequired) * 100),
isComplete: state.completedAt !== null,
isSkipped: state.skippedAt !== null,
steps: ONBOARDING_STEPS.map(step => ({
...step,
completed: state.completedSteps.includes(step.id),
current: state.currentStep === step.id
}))
};
}
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 · 437 lines · 4 tokens per session scan A b3c6300426c9
saas-onboarding is a skill published in the GitHub repository TheWayWithin/agent-11 (15 stars, last pushed 15d ago), licensed MIT. It adds 4 tokens to every session and 2,942 once invoked, about $0.0000 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-04.
Other skills, from other repositories
gsd-sketch
Sketch UI/design ideas with throwaway HTML mockups, or propose what to sketch next (frontier mode).
gsd-ui-phase
Generate UI design contract (UI-SPEC.md) for frontend phases.
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
design-an-interface
Produce 3+ radically different designs for a module, API, or interface, compare them in prose, and synthesize a recommendation. Use when asked to "design an interface", "shape this API", "design it twice", "explore module boundaries", or when planning a new deep module and the first idea is unlikely to be the best.…
design-to-code
Mockup-to-component pipeline using Google Stitch, 21st.dev, and Storybook MCP. Accepts a screenshot, a description, or a URL and produces production-ready React components, checking existing Storybook components before generating anything new. Use when implementing UI from a mockup or screenshot. To call the MCP tool…
design-ship
One-shot pipeline turning a claude.ai/design link into a pull request: scaffold via /ork:design-import, stories and specs via /ork:cover, browser verification via /ork:expect, then open the PR. Use when a design link should come back as a PR with no intermediate steps; if all you need is the components written to…