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/customer-journey-mapping)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/customer-journey-mapping"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/customer-journey-mapping/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/customer-journey-mapping"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/customer-journey-mapping.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.00050 | $0.00972 |
| Opus 5 | $0.00025 | $0.00486 |
| Sonnet 5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
customer-journey-mapping 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 10d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Mapping
Map, analyze, and optimize the full customer journey from first touch to advocacy.
Journey Stages
| Stage | Customer Goal | Key Channels | Metrics |
|---|---|---|---|
| Awareness | Discover a solution exists | SEO, social, ads, PR, referral | Impressions, reach, brand searches |
| Consideration | Evaluate options | Blog, reviews, comparison, webinar | Time on site, pages/session, content downloads |
| Decision | Choose and purchase | Pricing page, demo, trial, sales | Conversion rate, CAC, time to close |
| Onboarding | Get initial value | Welcome email, docs, setup wizard | Activation rate, time to value, support tickets |
| Retention | Continue getting value | Product, email, success team | NRR, usage frequency, NPS |
| Advocacy | Recommend to others | Referral, review, community | NPS, referral rate, review count |
Journey Map Template
For each stage, document:
### [Stage Name]
**Customer goal:** What are they trying to accomplish?
**Emotional state:** How do they feel? (confident, anxious, frustrated, delighted)
**Touchpoints:**
- [Channel 1]: [Specific interaction]
- [Channel 2]: [Specific interaction]
**Pain points:**
- [What causes friction or frustration]
**Opportunities:**
- [How to improve the experience]
**Key metric:** [Primary measurement]
**Drop-off risk:** [What causes people to leave at this stage]
Touchpoint Inventory
Common B2B SaaS Touchpoints
| Stage | Touchpoint | Owner |
|---|---|---|
| Awareness | Google search result | SEO/Content |
| Awareness | LinkedIn ad | Paid Media |
| Awareness | Blog post | Content |
| Consideration | Product page | Marketing |
| Consideration | Case study | Marketing |
| Consideration | Demo request form | Marketing |
| Decision | Sales demo | Sales |
| Decision | Pricing page | Product/Marketing |
| Decision | Proposal/contract | Sales |
| Onboarding | Welcome email sequence | CRM/CS |
| Onboarding | Setup wizard | Product |
| Onboarding | First value moment | Product |
| Retention | Feature adoption email | Product/CRM |
| Retention | QBR/check-in | CS |
| Retention | Product updates | Product |
| Advocacy | NPS survey | CS |
| Advocacy | Referral program | Growth |
| Advocacy | Case study request | Marketing |
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.
- 10d ago First seen · 110 lines · 50 tokens per session scan A 5b981a7bb193
customer-journey-mapping is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (134 stars, last pushed 3mo ago), licensed MIT. It adds 50 tokens to every session and 972 once invoked, about $0.0003 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.