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.
git clone --depth 1 https://github.com/rajitsaha/100xprismWrote 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/rules/rajitsaha/100xprism/signup-flow-cro)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/signup-flow-cro"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/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/rules/rajitsaha/100xprism/signup-flow-cro"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/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.00026 | $0.01983 |
| Opus 5 | $0.00013 | $0.00992 |
| Sonnet 5 | $0.00005 | $0.00397 |
| Haiku 4.5 | $0.00003 | $0.00198 |
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 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Signup Flow CRO
Reduce signup friction, increase completion rates, and set users up for successful activation.
Initial Assessment
Product context: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it first and tailor output to it; only ask for what it doesn't cover.
Before recommending, understand:
- Flow Type — free trial signup, freemium account creation, paid account creation, waitlist/early access, B2B vs B2C
- Current State — number of steps/screens, required fields, current completion rate, where users drop off
- Business Constraints — data genuinely needed at signup, compliance requirements, what happens immediately after signup
Core Principles
1. Minimize Required Fields
Every field reduces conversion. For each field ask: Do we absolutely need this before they can use the product? Can we collect it later through progressive profiling? Can we infer it from other data?
Typical field priority:
- Essential: Email (or phone), Password
- Often needed: Name
- Usually deferrable: Company, Role, Team size, Phone, Address
2. Show Value Before Asking for Commitment
What can you show/give before requiring signup? Can they experience the product before creating an account? Reverse the order: value first, signup second.
3. Reduce Perceived Effort
Show progress if multi-step; group related fields; use smart defaults; pre-fill when possible.
4. Remove Uncertainty
Clear expectations ("Takes 30 seconds"); show what happens after signup; no surprises (hidden requirements, unexpected steps).
Field-by-Field Optimization
Single field (no confirmation field); inline format validation; check common typos (gmial.com → gmail.com); clear error messages.
Password
Show password toggle (eye icon); show requirements upfront, not after failure, with real-time requirement indicators; consider passphrase hints for strength. Better password UX: allow paste (don't disable); strength meter instead of rigid rules; consider passwordless options.
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 · 209 lines · 26 tokens per session scan A c250c08fe926
signup-flow-cro is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 26 tokens to every session and 1,983 once invoked, about $0.0001 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-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.