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/thatrebeccarae/claude-marketingWrote 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/thatrebeccarae/claude-marketing/pricing-strategy)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/pricing-strategy"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/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.00043 | $0.01077 |
| Opus 5 | $0.00022 | $0.00539 |
| Sonnet 5 | $0.00009 | $0.00215 |
| Haiku 4.5 | $0.00004 | $0.00108 |
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 8d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pricing Strategy
Pricing model design, competitive analysis, and pricing page optimization.
Pricing Models
| Model | How It Works | Best For | Risk |
|---|---|---|---|
| Per-seat | Price per user/month | Collaboration tools | Discourages adoption |
| Usage-based | Pay for what you use | APIs, infrastructure | Revenue unpredictability |
| Tiered | Feature-gated plans | SaaS with clear feature tiers | Complexity, feature gating frustration |
| Freemium | Free tier + paid upgrades | PLG, network effects | Low conversion (2-5% typical) |
| Flat-rate | One price for everything | Simple products | Leaves money on table |
| Hybrid | Base + usage or seat + usage | Complex products | Pricing complexity |
| Per-unit | Price per resource (project, site) | Agencies, multi-property | Usage ceiling anxiety |
Value Metric Selection
The value metric is what you charge for (seats, API calls, revenue managed, etc.).
Good value metric criteria:
- Scales with customer value — as they get more value, they naturally pay more
- Easy to understand — customer can predict their bill
- Measurable — you can track and bill accurately
- Controllable — customer can influence their usage
| Product Type | Common Value Metrics |
|---|---|
| Email marketing | Contacts, emails sent |
| Analytics | Events tracked, monthly users |
| CRM | Seats, contacts |
| Infrastructure | Compute hours, storage, requests |
| E-commerce platform | GMV, orders, SKUs |
| Design tools | Seats, projects, exports |
Competitive Pricing Analysis
Analysis Framework
- Inventory competitors — list all direct and indirect alternatives
- Map pricing models — how does each charge?
- Normalize to common unit — price per seat/month at comparable usage
- Position on value map — plot price vs. feature completeness
- Identify gaps — underserved price points or segments
Positioning Strategies
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.
- 8d ago First seen · 115 lines · 43 tokens per session scan A a55fb0190e4c
pricing-strategy is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (132 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,077 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-08-30.
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.