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 eddiebelaval/squire --skill customer-journey-mappergit clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/eddiebelaval/squire/customer-journey-mapper)<a href="https://agentmods.dev/skills/eddiebelaval/squire/customer-journey-mapper"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/customer-journey-mapper/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/eddiebelaval/squire/customer-journey-mapper"><img src="https://agentmods.dev/badge/skills/eddiebelaval/squire/customer-journey-mapper.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.00013 | $0.00961 |
| Opus 5 | $0.00006 | $0.00481 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
Customer Journey Mapper 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 7d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Mapper
Visualize and optimize every step of the customer experience from first awareness to loyal advocacy. This skill helps you understand how customers actually interact with your brand, identify friction points, and design experiences that convert and retain.
Customers don't think in channels - they think in experiences. This skill provides frameworks for journey stage definition, touchpoint mapping, emotion tracking, and gap analysis. Transform siloed channel thinking into holistic experience design that meets customers where they are.
Essential for marketing strategists, CX professionals, product managers, and anyone designing customer experiences.
Core Workflows
Workflow 1: Journey Stage Mapping
- Stage Definition - Awareness, consideration, decision, retention, advocacy
- Customer Goals - What they're trying to achieve at each stage
- Questions and Concerns - What they need to know
- Touchpoint Inventory - Where they interact with brand
- Content Needs - Information required at each stage
- Conversion Actions - Desired behaviors per stage
- Transition Triggers - What moves them forward
Workflow 2: Touchpoint Analysis
- Channel Mapping - All interaction points
- Touchpoint Audit - Quality of each interaction
- Moment of Truth Identification - Critical experiences
- Friction Point Detection - Where customers get stuck
- Emotional Journey - Highs and lows of experience
- Gap Identification - Missing touchpoints
- Optimization Prioritization - Where to improve first
Workflow 3: Persona Journey Development
- Persona Selection - Which customer to map
- Scenario Definition - Specific journey context
- Step-by-Step Documentation - Detailed journey stages
- Thought Capture - What customer is thinking
- Emotion Mapping - How they feel at each point
- Pain Point Highlighting - Frustration moments
- Opportunity Tagging - Improvement possibilities
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.
- 7d ago First seen · 99 lines · 13 tokens per session scan A e992d59b3c08
Customer Journey Mapper is a skill published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 961 once invoked, about $0.0001 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 skills, from other repositories
Customer Journey Mapper
Map customer journeys to optimize touchpoints and experiences.
html-ppt-zhangzara-coral
OpenDesign's community-growth campaign across GitHub, Discord, and X: the loops, the content calendar, and the pipeline math. Built as a decision-grade marketing & GTM deck for growth team, community lead.
co-marketing
When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership…
market-pulse
When the user wants a comprehensive App Store market overview, daily/weekly market briefing, or combined view of chart movements, trending keywords, featured apps, and new releases. Also use when the user mentions "market overview", "what's happening on the App Store", "market briefing", "weekly report", "market…
beevibe-team-mesh-negotiation
Multi-round negotiation protocol — covers both initiator and peer roles. Use when about to call negotiate(), when receiving a intent block as a peer, or when receiving an 'escalated' sentinel from a blocked respondnegotiate. Covers proposal crafting, counter-strategy, deadlock detection, when to accept early…
manage-schemas
Creates, views, edits, deletes, and validates note schemas for the MCP Task Orchestrator in .taskorchestrator/config.yaml — the templates that define which notes agents must fill at each workflow phase. Also recommends schema designs from a library of workflow patterns (autonomous coding loops, spec-driven teams…