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 reatlat/fullstory-claude-plugin --skill journey-buildergit clone --depth 1 https://github.com/reatlat/fullstory-claude-pluginWrote 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/reatlat/fullstory-claude-plugin/journey-builder)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/journey-builder"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/journey-builder/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/reatlat/fullstory-claude-plugin/journey-builder"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/journey-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01037 |
| Opus 5 | $0.00027 | $0.00518 |
| Sonnet 5 | $0.00011 | $0.00207 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
journey-builder 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Journey Builder
Build Fullstory Journeys from plain English — no manual step-by-step configuration. Journeys show the most common paths users take through your product, where they drop off, and where they loop.
When to Use
- "Show me the most common paths users take from signup to first purchase"
- "What do users do right before they churn?"
- "Build a journey from the pricing page"
- "Update that onboarding journey to include mobile users"
- "Compare the journey for new vs returning users"
Mental Model
A Journey is a directed graph of user paths. Unlike a funnel (fixed linear steps), a Journey shows all observed paths between a start and end condition — including loops, detours, and unexpected routes. Use funnels when you know the exact steps; use Journeys when you want to discover what users actually do.
MCP Tools
| Tool | Purpose |
|---|---|
fullstory:build_journey |
Create a journey from natural language |
fullstory:get_journey |
Look up an existing journey by ID or name |
fullstory:compute_journey |
Execute and return journey results |
fullstory:update_journey |
Modify an existing journey without rebuilding |
Workflow
Step 1: Define the journey
Clarify the start point, end point (optional), and any constraints:
- Start: Where does the journey begin? (page, event, or user action)
- End: Where does it end? (optional — omit to see all paths from start)
- Time range: Always specify — narrow is faster
- Segment: Optional cohort filter (e.g., "mobile users only")
Step 2: Build or reuse
New journey:
fullstory:build_journey(query="users who land on /pricing, then either start a trial or view /features, then either upgrade or leave")
Reuse existing:
fullstory:get_journey(regex="onboarding")
→ returns journey_id, name, description, rendered definition
If found, compute it directly. If the user wants changes, use update_journey — don't rebuild from scratch.
Step 3: Compute
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 · 106 lines · 54 tokens per session scan A 2780f81423fb
journey-builder is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 54 tokens to every session and 1,037 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-30.
Other skills, from other repositories
roblox-input
Use when handling Roblox keyboard, mouse, gamepad, touch, motion input, or cross-platform action binding.
roblox-lighting
Use for Roblox lighting, atmosphere, day/night, or post-processing effects.
roblox-performance
Use when profiling Roblox performance or diagnosing FPS, memory, network, mobile, or hot-path problems.
roblox-growth-design
Use for growth diagnosis, discovery, retention, onboarding, experiments, LiveOps, and packaging.
roblox-networking
Use when validating RemoteEvent or RemoteFunction arguments, adding rate limits, designing server-authoritative systems, or preventing exploits.
roblox-ui-design
Use for Roblox UI composition, hierarchy, visual systems, style inheritance, accessibility, and design review.