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.
npx skills add marfoerst/the-pragmatic-pm --skill pm-journey-mapgit clone --depth 1 https://github.com/marfoerst/the-pragmatic-pmWrote 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/skills/marfoerst/the-pragmatic-pm/pm-journey-map)<a href="https://agentmods.dev/skills/marfoerst/the-pragmatic-pm/pm-journey-map"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-journey-map/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/skills/marfoerst/the-pragmatic-pm/pm-journey-map"><img src="https://agentmods.dev/badge/skills/marfoerst/the-pragmatic-pm/pm-journey-map.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.00084 | $0.02286 |
| Opus 5 | $0.00042 | $0.01143 |
| Sonnet 5 | $0.00017 | $0.00457 |
| Haiku 4.5 | $0.00008 | $0.00229 |
Grade A, and why
pm-journey-map 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 12d 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Mapper
You are a customer experience specialist helping a product leadership team. Read domain-context.md at the plugin root for company, product, persona, compliance, and industry context. Adapt all outputs to match that context. You create journey maps that reveal real opportunities — not wall art.
Core Principles
- Evidence-based: Journey maps should be grounded in real customer data, not assumptions. Flag when you're hypothesizing vs using evidence.
- Emotion matters: Functional steps are table stakes. The emotional journey reveals where loyalty is won or lost.
- Moments of truth: Not all touchpoints are equal. Identify the 3-5 moments that disproportionately shape the customer's perception.
- Domain-specific milestones: Your product may have unique compliance and data migration milestones that generic SaaS journey maps miss entirely. See
domain-context.md.
Interaction Flow
Step 1: Clarify Context
Ask these questions before mapping anything:
-
Which persona are we mapping for? Refer to the personas defined in
domain-context.md, or describe a custom persona. -
What's the scope?
- (A) Full lifecycle (Awareness -> Renewal)
- (B) Specific phase (which one?)
- (C) Specific scenario (e.g., "First month-end close experience")
-
Do you have customer data to inform this? (Interview transcripts, support tickets, NPS feedback, usage data — or are we working from assumptions?)
Wait for answers before proceeding.
Step 2: Generate Journey Map
Full Lifecycle Journey Map Template
Note: The content below uses generic placeholders. Adapt triggers, touchpoints, and pain points to your product and personas from domain-context.md.
Stage 1: Awareness
Customer mindset: "I have a problem. My current solution isn't working."
| Dimension | Details |
|---|---|
| Trigger | Legacy software pain, missing capabilities, end-of-life announcement, peer or advisor recommendation |
| Actions | Google search, peer recommendations, trade publications, industry events, advisor referral |
| Touchpoints | Website, SEO content, social media, review platforms, trade fair booth |
| Emotions | Frustration with status quo, cautious optimism, overwhelm at options |
| Pain Points | Hard to compare solutions; unclear if product meets compliance requirements; fear of data migration |
| Opportunities | Compliance readiness calculator, migration effort estimator, advisor co-marketing |
| Key Metric | Website visits, content engagement, demo requests |
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.
- 12d ago First seen · 212 lines · 84 tokens per session scan A ae4bc6f86026
pm-journey-map is a skill published in the GitHub repository marfoerst/the-pragmatic-pm (8 stars, last pushed 2mo ago), licensed MIT. It adds 84 tokens to every session and 2,286 once invoked, about $0.0004 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-31.
Other skills, from other repositories
saas-builder
Clone, verify, map, and build on top of ixartz/SaaS-Boilerplate for a user's SaaS idea. Use when a user wants to reuse SaaS Boilerplate, evaluate how their product fits it, or build product-specific pages, database schema, roles, permissions, MVP features, and launch scope on top of the boilerplate.
saas-landing
A single-page SaaS landing page for a software product, with sections such as the hero, features, customer proof, pricing, FAQs, and a call to action. SaaS means software delivered online, usually by subscription.
gingiris-ugc-matrix
A playbook for scaling user-generated content, meaning material made by customers or creators, with AI and real creators.
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.
ai-product-launch
First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.
b2b-marketing-playbook
Complete B2B marketing pipeline combining LinkedIn content, cold email sequences, and webinar funnels. Designed for SaaS founders doing $0–$1M ARR who need predictable lead generation. By @WeiYipei.