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/launch-strategy)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/launch-strategy"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/launch-strategy.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.00031 | $0.02423 |
| Opus 5 | $0.00015 | $0.01211 |
| Sonnet 5 | $0.00006 | $0.00485 |
| Haiku 4.5 | $0.00003 | $0.00242 |
Grade A, and why
launch-strategy 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 — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Strategy
Plan SaaS product launches and feature announcements that build momentum, capture attention, and convert interest into users.
Before Starting
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.
Core Philosophy
The best companies launch again and again — every feature, improvement, and update is a chance to capture attention. A strong launch isn't a single moment; it's getting the product into users' hands early, learning from real feedback, making a splash at every stage, and building momentum that compounds.
The ORB Framework
Structure launch marketing across three channel types. Everything should ultimately lead back to owned channels.
Owned Channels
You own the channel (though not the audience) — direct access without algorithms or platform rules.
Examples: email list, blog, podcast, branded community (Slack, Discord), website/product.
Why they matter: get more effective over time, no algorithm changes or pay-to-play, direct audience relationship, compounding content value.
Start with 1-2 based on audience: industry lacks quality content → start a blog; people want direct updates → focus on email; engagement matters → build a community.
Example — Superhuman: Built demand through an invite-only waitlist and one-on-one onboarding — every new user got a 30-minute live demo. This created exclusivity, FOMO, and word-of-mouth through owned relationships; years later their original onboarding materials still drive engagement.
Rented Channels
Platforms that provide visibility but you don't control — algorithms shift, rules change, pay-to-play increases.
Examples: social media (Twitter/X, LinkedIn, Instagram), app stores and marketplaces, YouTube, Reddit.
How to use: pick 1-2 platforms where your audience is active, drive traffic to owned channels, never rely on them as your only strategy.
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 · 224 lines · 2,423 tokens per session scan A 7c949772ab0b
launch-strategy is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 31 tokens to every session and 2,423 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.