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 bjorn-ingmanson/thefroject-plugins --skill customer-journey-mappinggit clone --depth 1 https://github.com/bjorn-ingmanson/thefroject-pluginsWrote 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/bjorn-ingmanson/thefroject-plugins/customer-journey-mapping)<a href="https://agentmods.dev/skills/bjorn-ingmanson/thefroject-plugins/customer-journey-mapping"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/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/skills/bjorn-ingmanson/thefroject-plugins/customer-journey-mapping"><img src="https://agentmods.dev/badge/skills/bjorn-ingmanson/thefroject-plugins/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.00068 | $0.01171 |
| Opus 5 | $0.00034 | $0.00585 |
| Sonnet 5 | $0.00014 | $0.00234 |
| Haiku 4.5 | $0.00007 | $0.00117 |
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 11d 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer Journey Mapping
Build a customer journey map covering awareness through renewal. The map is a working document that defines stages, signals, and ownership. CS playbooks, lifecycle marketing emails, support routing, and feature priorities all reference it.
Gather context
Ask if not provided:
- Product type — self-serve SaaS, sales-led SaaS, enterprise platform, marketplace, services.
- Sales motion — PLG (product-led), sales-led, hybrid.
- Touchpoints — what channels exist today (website, in-app, email, support, calls, community).
- Roles — who's involved (marketing, sales, CS, support, product, exec sponsor for enterprise).
Default lifecycle stages
For most B2B SaaS, the lifecycle has six stages. For self-serve/PLG, collapse stages 2-3.
| Stage | What happens | Owner | Key signal |
|---|---|---|---|
| Awareness | Customer encounters the brand | Marketing | First touch (web visit, social, referral) |
| Evaluation | Customer compares options | Marketing/Sales | Pricing/demo page visit, content engagement |
| Acquisition | Customer commits | Sales (or self-serve flow) | Closed-won, trial signup, paid conversion |
| Onboarding | Customer reaches first value | CS / Support | First key action completed |
| Adoption | Customer integrates the product into work | CS | Steady-state usage pattern |
| Expansion / Renewal | Customer grows or renews (or churns) | CS / AM | Renewal date hit; expansion deal opened |
Some products add: Advocacy (post-renewal customer recommends, refers, gives testimonial). Worth a stage if the program is mature.
For each stage, document
- Definition — one sentence.
- Entry criteria — what specifically gets a customer into this stage (no ambiguity).
- Exit criteria — what gets them to the next stage (or out — churn).
- Owner — single named role (not "marketing and CS").
- Signals to monitor — leading indicators that a customer is healthy or stuck in this stage.
- Plays — what the owner does (touchpoints, communications, interventions).
- Time-in-stage benchmark — typical duration; flag accounts that exceed it.
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.
- 11d ago First seen · 104 lines · 68 tokens per session scan A 1cb72665c226
customer-journey-mapping is a skill published in the GitHub repository bjorn-ingmanson/thefroject-plugins (1 stars, last pushed 2mo ago), licensed MIT. It adds 68 tokens to every session and 1,171 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.