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/form-cro)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/form-cro"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/form-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/form-cro"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/form-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.00030 | $0.02116 |
| Opus 5 | $0.00015 | $0.01058 |
| Sonnet 5 | $0.00006 | $0.00423 |
| Haiku 4.5 | $0.00003 | $0.00212 |
Grade A, and why
form-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 — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Form CRO
Maximize form completion rates while capturing the data that matters.
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, identify:
- Form Type — lead capture (gated content, newsletter), contact, demo/sales request, application, survey/feedback, checkout, quote request
- Current State — field count, current completion rate, mobile vs. desktop split, where users abandon
- Business Context — what happens with submissions, which fields are actually used in follow-up, compliance/legal requirements
Core Principles
1. Every Field Has a Cost
Each field reduces completion. Rule of thumb: 3 fields = baseline; 4-6 fields = 10-25% reduction; 7+ fields = 25-50%+ reduction. For each field ask: Is it absolutely necessary before we can help them? Can we get it another way? Can we ask later?
2. Value Must Exceed Effort
Clear value proposition above the form; make what they get obvious; reduce perceived effort (field count, labels).
3. Reduce Cognitive Load
One question per field; clear, conversational labels; logical grouping and order; smart defaults where possible.
Field-by-Field Optimization
Single field, no confirmation; inline validation; typo detection (did you mean gmail.com?); proper mobile keyboard.
Name
Test single "Name" vs. First/Last — single field reduces friction; split only if personalization requires it.
Phone Number
Make optional if possible; if required, explain why; auto-format as they type; handle country codes.
Company/Organization
Auto-suggest for faster entry; enrich after submission (Clearbit, etc.); consider inferring from email domain.
Job Title/Role
Dropdown if categories matter; free text if wide variation; consider making optional.
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 · 245 lines · 30 tokens per session scan A 7bea899f9cd6
form-cro is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 2,116 once invoked, about $0.0002 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.