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 commands/maigentic/stratarts/onboarding-flow-optimizergit clone --depth 1 https://github.com/maigentic/stratartsWrote 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/commands/maigentic/stratarts/onboarding-flow-optimizer)<a href="https://agentmods.dev/commands/maigentic/stratarts/onboarding-flow-optimizer"><img src="https://agentmods.dev/badge/commands/maigentic/stratarts/onboarding-flow-optimizer.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 | $0.00053 | $0.08685 |
| Opus 5 | $0.00026 | $0.04342 |
| Sonnet 5 | $0.00011 | $0.01737 |
| Haiku 4.5 | $0.00005 | $0.00869 |
Grade A, and why
onboarding-flow-optimizer 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 5d 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 — 830 lines — stays where its author put it; the contents beside it link to each section on GitHub.
onboarding-flow-optimizer
Mission: Optimize the onboarding experience to reduce time-to-value, increase activation rates, and improve early retention (D1-D7). Design clear paths to the "aha moment" through checklists, product tours, educational content, and personalized onboarding flows.
STEP 0: Pre-Generation Verification
Before generating the HTML output, verify all required data is collected:
Header & Score Banner
-
{{BUSINESS_NAME}}- Company/product name -
{{DATE}}- Report generation date -
{{ACTIVATION_RATE}}- Current activation rate (e.g., "47%") -
{{TARGET_RATE}}- Target activation rate (e.g., "65%") -
{{TIME_TO_ACTIVATE}}- Median time to activate (e.g., "18h") -
{{CHECKLIST_STEPS}}- Number of onboarding steps (e.g., "5") -
{{D7_RETENTION}}- Day 7 retention rate (e.g., "52%") -
{{AHA_MOMENT}}- Short aha moment description (e.g., "First Task Completed")
Executive Summary
-
{{EXECUTIVE_SUMMARY}}- 2-3 paragraph overview with key insights and interventions -
{{ACTIVATION_EVENT}}- Full activation event definition -
{{ACTIVATION_DESCRIPTION}}- Why this event represents the aha moment
Funnel Analysis
-
{{FUNNEL_STEPS}}- 5+ funnel steps with users, conversion %, drop-off %- Each step: step name, bar width, user count, drop-off percentage
Onboarding Checklist
-
{{CHECKLIST_STEPS}}- 3-5 numbered steps- Each step: title, reason (why it matters), time estimate
Product Tour
-
{{TOUR_STEPS}}- 5-7 tour steps- Each step: number, title, highlight message, user action
Educational Content
-
{{CONTENT_CARDS}}- 5-6 content types- Each card: icon, type label, description
Personalized Paths
-
{{PATH_CARDS}}- 2-4 user segments- Each path: segment name, goal, 3-4 checklist steps
Email Sequence
-
{{EMAIL_ITEMS}}- 5 emails (Day 0, 1, 3, 5, 7)- Each email: day label, subject line, body description
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.
- 5d ago First seen · 830 lines · 53 tokens per session scan A cd7ca92fb780
onboarding-flow-optimizer is a command published in the GitHub repository maigentic/stratarts (39 stars, last pushed 6mo ago), licensed MIT. It adds 53 tokens to every session and 8,685 once invoked, about $0.0003 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 commands, from other repositories
help
Show greatcto commands, key concepts, and admin board URL. Use when you don't remember a command or you are new to greatcto.
dotnet-teach
One-time setup that scans a .NET backend project, learns its conventions and architecture, and writes them to CLAUDE.md for future sessions.
study-help
Explain the agentic-study-environment harness — everything it offers, or a specific skill, domain overlay, session type, or convention if you name one.
ux-onboarding
Get familiar with a project's UX/design choices and patterns — a guided, part-by-part walkthrough that sends you to read the real code, checks your understanding with questions, and has you reimplement a small recent change.
scholastic
Analyze through Modern Scholastic method (quaestio disputata).
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.