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 agentmods add skills/hoavdc/codexkit/codexkit-customer-journey-mappernpx skills add hoavdc/CodexKit --skill codexkit-customer-journey-mappergit clone --depth 1 https://github.com/hoavdc/CodexKitWrote 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/hoavdc/codexkit/codexkit-customer-journey-mapper)<a href="https://agentmods.dev/skills/hoavdc/codexkit/codexkit-customer-journey-mapper"><img src="https://agentmods.dev/badge/skills/hoavdc/codexkit/codexkit-customer-journey-mapper.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 | $0.00074 | $0.01006 |
| Opus 5 | $0.00037 | $0.00503 |
| Sonnet 5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
codexkit-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 3d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Mapper
Purpose
Visualize and analyze the complete customer experience — from first awareness to advocacy — identifying pain points, opportunities, and moments that drive loyalty or churn.
When to use
- designing or redesigning the customer experience for a product or service
- investigating why customers churn at a specific stage
- aligning marketing, sales, and CS teams around the customer lifecycle
- preparing for a CX improvement initiative
When not to use
- internal process mapping (use process-mapper)
- sales pipeline or CRM workflow design
- individual customer troubleshooting
Inputs
- customer persona(s) — who is the journey for?
- product or service being mapped
- known lifecycle stages (or use the default 7-stage model)
- available customer data: NPS, CSAT, support tickets, analytics
- known pain points or complaints from customers
- current touchpoints across channels
Procedure
- Define the persona — who are we mapping the journey for?
- Demographics, goals, frustrations, and decision drivers
- Map 7 lifecycle stages (adapt as needed):
- Awareness → Consideration → Purchase → Onboarding → Adoption → Retention → Advocacy
- For each stage, document:
- Customer goal: what are they trying to accomplish?
- Actions: what specific things do they do?
- Touchpoints: where do they interact with us? (website, app, email, support, person)
- Emotions: how do they feel? (excited, confused, frustrated, delighted)
- Pain points: what barriers or friction do they encounter?
- Moments of Truth (MoT): decisions that make-or-break the relationship
- Identify Moments of Truth — classify each:
- Zero MoT (ZMOT): when they first discover you
- First MoT: first purchase or sign-up decision
- Second MoT: first real usage experience
- Ultimate MoT: when they decide to advocate or churn
- Score each stage using available data:
- CSAT or NPS per stage
- Drop-off rates between stages
- Average time-in-stage
- Support ticket volume per stage
- Identify improvement opportunities — prioritize by:
- Impact on retention or revenue
- Effort to fix
- Strategic alignment
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 111 lines · 74 tokens per session scan A 6f5118cf60ba
codexkit-customer-journey-mapper is a skill published in the GitHub repository hoavdc/CodexKit (21 stars, last pushed 3mo ago), licensed MIT. It adds 74 tokens to every session and 1,006 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-30.
Other skills, from other repositories
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
reducing-aigc-detection
Systematically reduce AIGC detection rates in academic papers (Chinese/English). Analyzes detection reports, identifies high-impact sections, applies multi-layer rewriting strategies preserving formatting/footnotes, and verifies results. Supports 维普/知网/Turnitin platforms.
architecting-security
安全架构与治理：威胁建模 (STRIDE/PASTA/LINDDUN)、零信任身份架构、IAM/SSO/MFA/PAM、合规框架 (SOC2/PCI/HIPAA/GDPR)、DLP、隐私工程、安全控制设计。Use when designing security architecture, threat modeling new systems, implementing zero-trust identity, designing IAM/SSO/PAM, building compliance evidence chains, or planning privacy-by-design.
defending-applications
Application security defense knowledge for builders. Covers Web/API/GraphQL hardening (XSS/SQLi/SSRF/IDOR/BOLA/Mass Assignment/deserialization/upload/path traversal), authentication/authorization (OAuth 2.0/OIDC/JWT/Session/Cookie/SAML/SSO), and LLM application security (prompt injection, jailbreak, RAG poisoning…
detecting-and-responding
蓝队与紫队工程：检测规则编写、SIEM/EDR 调优、事件响应、数字取证、威胁狩猎、ATT&CK 映射、紫队演练闭环。Use when writing Sigma/YARA detection rules, tuning SIEM noise, responding to security incidents, conducting forensic analysis, hunting threats, or running purple team exercises.
securing-cloud-and-supply-chain
云原生与软件供应链安全防御。容器/K8s 加固、Service Mesh、CI/CD 安全、SLSA/SBOM/Sigstore、云 IAM、Secrets 管理、IaC 安全。Use when hardening Kubernetes clusters, auditing CI/CD pipelines, implementing supply chain security, managing cloud IAM, or reviewing IaC code.