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 charlieviettq/awesome-agent-skill --skill biz-customer-journeygit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/biz-customer-journey)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/biz-customer-journey"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-customer-journey/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/charlieviettq/awesome-agent-skill/biz-customer-journey"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/biz-customer-journey.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.00085 | $0.01615 |
| Opus 5 | $0.00043 | $0.00807 |
| Sonnet 5 | $0.00017 | $0.00323 |
| Haiku 4.5 | $0.00009 | $0.00161 |
Grade A, and why
"biz-customer-journey" 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.
This is a copy
94% identical to biz-customer-journey — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Mapping
Overview
Customer Journey Mapping visualizes the entire experience a customer has with a brand — from first awareness through post-purchase advocacy. It identifies touchpoints, emotions, pain points, and opportunities at each stage. The goal is to find and fix where customers get stuck, frustrated, or leave.
When to Use
Trigger conditions:
- User wants to improve conversion rates across the funnel
- User needs to understand where customers drop off
- User designing or redesigning a customer experience
- User asks "where are we losing customers?" or "what's the user experience like?"
When NOT to use:
- For market segmentation → use STP
- For product feature decisions → use Jobs to Be Done
- For one-time strategic analysis → use SWOT
Framework
IRON LAW: Map the Customer's Reality, Not Your Ideal
The journey map must reflect what customers ACTUALLY experience, not what
you designed or intended. If customers Google your brand and find negative
reviews (reality), don't map "customer visits our website" (ideal).
Base the map on data: analytics, customer interviews, support tickets,
heatmaps — not internal assumptions.
IRON LAW: Every Touchpoint Needs an Emotion
A journey map without emotions is a process diagram. At every touchpoint,
note the customer's emotional state: confident, confused, frustrated,
delighted. Emotions predict behavior better than process steps.
The Five Stages
1. Awareness — Customer realizes they have a need or discovers your brand
- Touchpoints: ads, social media, word-of-mouth, search results, content
- Key question: "How do they first encounter us?"
2. Consideration — Customer evaluates options and compares alternatives
- Touchpoints: website, reviews, comparisons, demos, sales conversations
- Key question: "What information do they seek and where?"
3. Decision — Customer chooses and purchases
- Touchpoints: checkout, pricing page, sales closing, contract signing
- Key question: "What friction exists at the purchase moment?"
What ships with it
2 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.
- 9d ago First seen · 157 lines · 85 tokens per session scan A c5b342cddebd
"biz-customer-journey" is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (26 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 1,615 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to biz-customer-journey, differing in 8 lines, and is treated as a copy.
Other skills, from other repositories
agent-orchestrator
Meta-skill que orquestra todos os agentes do ecossistema. Scan automatico de skills, match por capacidades, coordenacao de workflows multi-skill e registry management.
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
skill-curator
A Chinese-language evaluator for deciding whether developer tools and agent resources are suitable for a curated collection. It checks real repositories, installation paths, activity, duplicates, and security boundaries using evidence.
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.
plugin-dev-workflow
Guide plugin development workflow — editing skills, agents, hooks, or eval framework in this repo. Use when modifying files in plugins/elixir-phoenix/, lab/eval/, or lab/autoresearch/. Ensures changes pass eval, lint, and tests before committing.