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/pricing-strategy)<a href="https://agentmods.dev/rules/rajitsaha/100xprism/pricing-strategy"><img src="https://agentmods.dev/badge/rules/rajitsaha/100xprism/pricing-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.00036 | $0.01320 |
| Opus 5 | $0.00018 | $0.00660 |
| Sonnet 5 | $0.00007 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
pricing-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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy
Design pricing that captures value, drives growth, and aligns with customer willingness to pay.
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.
Gather (ask if not provided):
- Business Context — product type (SaaS, marketplace, e-commerce, service); current pricing; target market (SMB, mid-market, enterprise); GTM motion (self-serve, sales-led, hybrid)
- Value & Competition — primary value delivered; alternatives customers consider; competitor pricing
- Current Performance — conversion rate, ARPU, churn; pricing feedback from customers/prospects
- Goals — optimizing for growth, revenue, or profitability? Moving upmarket or downmarket?
Pricing Fundamentals
The Three Pricing Axes
- Packaging — what's included at each tier (features, limits, support level) and how tiers differ
- Pricing Metric — what you charge for (per user, per usage, flat fee) and how price scales with value
- Price Point — actual dollar amounts; perceived value vs. cost
Value-Based Pricing
Price on value delivered, not cost to serve: customer's perceived value is the ceiling; next best alternative is the floor for differentiation; your cost to serve is only a baseline, not the basis.
Key insight: Price between the next best alternative and perceived value.
Value Metrics
The value metric is what you charge for — it should scale with the value customers receive. Good value metrics align price with value delivered, are easy to understand, scale as the customer grows, and are hard to game.
Common Value Metrics
| Metric | Best For | Example |
|---|---|---|
| Per user/seat | Collaboration tools | Slack, Notion |
| Per usage | Variable consumption | AWS, Twilio |
| Per feature | Modular products | HubSpot add-ons |
| Per contact/record | CRM, email tools | Mailchimp |
| Per transaction | Payments, marketplaces | Stripe |
| Flat fee | Simple products | Basecamp |
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 · 159 lines · 1,320 tokens per session scan A 99c857f74387
pricing-strategy is a cursor rule published in the GitHub repository rajitsaha/100xprism (10 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 1,320 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.