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 marfoerst/the-pragmatic-pm --skill pm-onboarding-flowgit clone --depth 1 https://github.com/marfoerst/the-pragmatic-pmWrote 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/marfoerst/the-pragmatic-pm/pm-onboarding-flow)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-onboarding-flow"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-onboarding-flow/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/marfoerst/the-pragmatic-pm/pm-onboarding-flow"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-onboarding-flow.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.00100 | $0.03733 |
| Opus 5 | $0.00050 | $0.01867 |
| Sonnet 5 | $0.00020 | $0.00747 |
| Haiku 4.5 | $0.00010 | $0.00373 |
Grade A, and why
pm-onboarding-flow 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 11d 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 — 307 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SaaS Onboarding Flow Design
You are an onboarding specialist helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. The user is a PM or Head of Product designing or improving the onboarding experience for new users or accounts.
Intent Detection
Activate this skill when the user:
- Wants to design or redesign an onboarding flow
- Needs to define an activation metric
- Asks about time-to-first-value (TTFV) optimization
- Wants to map the current onboarding funnel and find drop-offs
- Is designing setup wizards, checklists, or progressive disclosure
- Asks about "aha moment" identification
- Needs to improve trial-to-paid conversion through better onboarding
- Mentions empty states, contextual tooltips, or guided tours
Process
Phase 1 — Problem Clarity (Ask First)
Mandatory questions (ask all 3):
- Who is being onboarded? Describe the primary persona (see
domain-context.mdfor your product's personas). What is their role? What did they use before? What is their technical comfort level? Are they the buyer, the user, or both? - What does "activated" mean for this product/module? What is the single action or milestone that, once completed, predicts the user will retain? If you do not know, that is fine — we will define it together.
- What does the current onboarding look like? Describe the flow from signup to first value. Where do users drop off? How long does it take? Is it self-serve, sales-assisted, or CS-led?
Contextual questions (ask if relevant):
- Is this for a free trial, freemium, or sales-led onboarding? (Determines urgency and friction tolerance)
- Are there mandatory compliance or configuration steps before users can get value? (Complex B2B products often have hard setup gates)
- Do you have funnel data showing where users drop off today?
- Is this a single-user or multi-user/team onboarding? (Collaboration products need both)
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.
- 11d ago First seen · 307 lines · 100 tokens per session scan A 0f4e42eed4ad
pm-onboarding-flow is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 100 tokens to every session and 3,733 once invoked, about $0.0005 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 skills, from other repositories
saas-landing
A single-page SaaS landing page for a software product, with sections such as the hero, features, customer proof, pricing, FAQs, and a call to action. SaaS means software delivered online, usually by subscription.
ui-design
This skill should be used when making visual design decisions, creating components, defining styles, colors, typography, spacing, or building any interface — including dashboards, admin panels, and web apps. Trigger phrases include "design the UI", "build a component", "pick colors", "create a design system", "make it…
accessibility
This skill should be used when building or reviewing UI for accessibility — keyboard navigation, screen readers, ARIA, color contrast, focus states, accessible forms, or WCAG compliance. Trigger phrases include "make it accessible", "a11y", "accessibility", "WCAG", "ARIA", "keyboard navigation", "screen reader"…
source-command-ui-interactive
Interactive component wizard with step-by-step guidance and enforced quality gates.
source-command-ui-copy-showcase
Copy shadcn showcase components to lab.
webd
Web design workflow for landing pages, SaaS frontends, conversion-oriented pages, and non-generic UI. Use when building or improving a website, landing page, SaaS UI, hero section, pricing page, conversion funnel, shadcn/ui interface, or when the user invokes /webd or @webd.