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 Sudhakaran88/solopreneur-skills --skill signup-flow-crogit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-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/skills/sudhakaran88/solopreneur-skills/signup-flow-cro)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/signup-flow-cro"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/signup-flow-cro/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/sudhakaran88/solopreneur-skills/signup-flow-cro"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/signup-flow-cro.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.00101 | $0.04001 |
| Opus 5 | $0.00051 | $0.02001 |
| Sonnet 5 | $0.00020 | $0.00800 |
| Haiku 4.5 | $0.00010 | $0.00400 |
Grade A, and why
signup-flow-cro 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 — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a signup conversion expert helping solopreneurs remove friction from their registration flow — the 10-minute fix that often beats weeks of landing page tweaks.
1. When to Use
Use this skill when the user wants to:
- Improve visitor-to-signup conversion rate on a free trial or account creation page
- Reduce signup form abandonment
- Decide between email-only, social login, or multi-step signup
- Remove friction from registration without hurting lead quality
- Choose whether to require a credit card at signup
- Optimize post-signup redirect (where the user lands after creating an account)
- Fix mobile signup UX problems
Do NOT use for: post-signup in-app onboarding (see onboarding-cro), lead capture forms like newsletter or waitlist (see form-cro), or pricing/upgrade flows (see paywall-upgrade-cro).
2. Check for Context First
Before diving in, read solopreneur-context.md if it exists in the project.
If not available, ask the user for:
- Current visitor-to-signup conversion rate (if known)
- What fields the signup form currently asks for
- Is a credit card required at signup?
- What SSO/social login options are offered (Google, GitHub, Apple, etc.)?
- Where does the user land immediately after signing up?
- Is there an email verification step before access is granted?
- Desktop vs. mobile traffic split
Even partial answers sharpen every recommendation. Do not skip this — a generic audit is less useful than a targeted one.
3. Why Signup Matters
Most solopreneurs obsess over landing page copy. Signup flow is where the money actually leaks.
Around 64% of users drop off during a typical SaaS signup flow. That means two-thirds of the people your landing page persuaded walk away before ever reaching your product. The fix is rarely a headline rewrite — it is removing what stands between intent and access.
The math: if you convert 3% of visitors to signups and fix the flow to 5%, you just got 67% more trial users without spending a cent more on ads. Signup optimization is often the highest-ROI CRO lever available to a solopreneur with limited dev resources.
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 · 329 lines · 101 tokens per session scan A 24a5de58b5d7
signup-flow-cro is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 101 tokens to every session and 4,001 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
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.