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/icp-research)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/icp-research"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/icp-research/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/thatrebeccarae/claude-marketing/icp-research"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/icp-research.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.00048 | $0.02471 |
| Opus 5 | $0.00024 | $0.01236 |
| Sonnet 5 | $0.00010 | $0.00494 |
| Haiku 4.5 | $0.00005 | $0.00247 |
Grade A, and why
icp-research 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 9d 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 — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ICP Research
Build comprehensive ideal customer profiles for targeted marketing, including community discovery and voice-of-customer language extraction.
Workflow
1. Gather Product Context
- What do you sell?
- Key features and differentiators
- Pricing model and range
- Current customers (who buys today?)
2. Define Market
- Industry / vertical
- Company size (employees, revenue)
- Geography
- B2B vs. B2C vs. B2B2C
3. Build Persona
Demographics:
- Job title and seniority level
- Department and reporting structure
- Company size and revenue range
- Industry and sub-vertical
- Geography and timezone
Psychographics:
- Daily responsibilities (what fills their calendar)
- Goals they are measured on (KPIs, OKRs)
- Frustrations and daily friction
- Career aspirations
- How they stay informed (publications, podcasts, communities)
Buying Behavior:
- Who influences the decision?
- Who approves the budget?
- What is the buying process? (self-serve, demo, RFP, committee)
- Evaluation criteria (price, features, support, integration)
- Typical buying timeline
4. Map Pain Points
| Category | Questions to Answer |
|---|---|
| Time | What takes too long? What manual work do they hate? |
| Money | Where are they wasting budget? What costs too much? |
| Risk | What keeps them up at night? What could go wrong? |
| Quality | Where is output inconsistent or error-prone? |
| Growth | What blocks them from scaling? |
Score each pain point: Frequency (1-10) x Intensity (1-10) = Priority Score
5. Identify Objections
| Objection Type | Response Strategy |
|---|---|
| Price | ROI calculation, cost of inaction, payment flexibility |
| Time | Quick setup, done-for-you options, time-to-value metrics |
| Trust | Social proof, case studies, free trial/pilot, guarantees |
| Need | Cost of status quo, competitor pressure, market trends |
| Authority | Executive summary, ROI one-pager, pilot proposal |
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.
- 9d ago First seen · 340 lines · 48 tokens per session scan A 55bb82843a4e
icp-research is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (133 stars, last pushed 3mo ago), licensed MIT. It adds 48 tokens to every session and 2,471 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.