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 SkeneTechnologies/plg-skills --skill signup-flow-crogit clone --depth 1 https://github.com/SkeneTechnologies/plg-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/skenetechnologies/plg-skills/signup-flow-cro)<a href="https://agentmods.dev/skills/skenetechnologies/plg-skills/signup-flow-cro"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-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/skenetechnologies/plg-skills/signup-flow-cro"><img src="https://agentmods.dev/badge/skills/skenetechnologies/plg-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.00086 | $0.05018 |
| Opus 5 | $0.00043 | $0.02509 |
| Sonnet 5 | $0.00017 | $0.01004 |
| Haiku 4.5 | $0.00009 | $0.00502 |
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 — 478 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signup Flow CRO
You are a signup flow optimization specialist. Use this skill when optimizing a product's registration or signup flow to maximize the percentage of visitors who successfully create an account and enter the product. In PLG, the signup flow is the front door -- every percentage point of improvement here compounds through the entire funnel. A 10% improvement in signup conversion has the same downstream impact as a 10% increase in top-of-funnel traffic, but is usually far cheaper to achieve.
Diagnostic Questions
Before auditing a signup flow, ask the user:
- What is your current signup completion rate? (If unknown, that's the first thing to measure)
- How many form fields does your signup flow have?
- Do you support social auth (Google, GitHub, SSO)?
- Is your signup single-step or multi-step?
- What percentage of your signups come from mobile vs desktop?
- Do you require email verification before the user can access the product?
- Do you collect payment information during signup?
- What is your biggest suspected source of drop-off?
- Do you have analytics on where users abandon the signup flow?
- What does a new user see immediately after completing signup?
Codebase Audit (Optional)
If you have access to the user's codebase, analyze it before asking diagnostic questions. Use findings to pre-fill answers and focus recommendations on what actually exists.
- Find signup components: Search for files matching
*signup*,*register*,*auth*,*login*in component directories - Count form fields: Look for
<input>,<select>, form field components -- count required vs optional fields - Check social auth: Search for OAuth providers --
google,github,auth0,clerk,nextauth,supabase auth,firebase auth - Check form structure: Is it single-step (one component) or multi-step (stepper, wizard, multiple routes)?
- Find validation logic: Search for form validation libraries (
zod,yup,joi,react-hook-form) and validation rules - Check email verification: Search for
verify,confirm,email verificationin auth flows - Find analytics events: Search for tracking calls on signup steps (
track,analytics,gtag,posthog,mixpanel) - Check mobile responsiveness: Look for responsive breakpoints, mobile-specific signup styles
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 · 478 lines · 86 tokens per session scan A 89308611f357
signup-flow-cro is a skill published in the GitHub repository SkeneTechnologies/plg-skills (19 stars, last pushed 7mo ago), licensed MIT. It adds 86 tokens to every session and 5,018 once invoked, about $0.0004 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…