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/popup-cro)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/popup-cro"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/popup-cro.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.1 | $0.00033 | $0.02375 |
| Opus 5 | $0.00016 | $0.01188 |
| Sonnet 5 | $0.00007 | $0.00475 |
| Haiku 4.5 | $0.00003 | $0.00237 |
Grade A, and why
popup-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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Popup CRO
Create popups that convert without annoying users or damaging brand perception.
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:
- Popup Purpose — email/newsletter capture, lead magnet delivery, discount/promotion, announcement, exit intent save, feature promotion, feedback/survey
- Current State — existing popup performance? triggers used? user complaints or feedback? mobile experience?
- Traffic Context — traffic sources (paid, organic, direct); new vs. returning visitors; page types where shown
Core Principles
- Timing is everything — too early = annoying interruption; too late = missed opportunity; right time = helpful offer at the moment of need.
- Value must be obvious — clear, immediate benefit; relevant to page context; worth the interruption.
- Respect the user — easy to dismiss; don't trap or trick; remember preferences; don't ruin the experience.
Trigger Strategies
Time-Based
"Show after 5 seconds" is not recommended; "after 30-60 seconds" (proven engagement) is better. Best for general site visitors.
Scroll-Based
Typically 25-50% scroll depth — indicates content engagement. Best for blog posts and long-form content. Example: "You're halfway through—get more like this."
Exit Intent
Detects cursor moving to close/leave — last chance to capture value. Best for e-commerce and lead gen. Mobile alternative: back button or scroll up.
Click-Triggered
User initiates (clicks button/link), so zero annoyance. Best for lead magnets, gated content, demos. Example: "Download PDF" → popup form.
Page Count / Session-Based
After visiting X pages — indicates research/comparison behavior. Best for multi-page journeys. Example: "Been comparing? Here's a summary..."
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 · 264 lines · 33 tokens per session scan A ba7f1c085637
popup-cro is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 2,375 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.