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 user-journeygit 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/user-journey)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/user-journey"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/user-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/reatlat/fullstory-claude-plugin/user-journey"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/user-journey.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.00052 | $0.01062 |
| Opus 5 | $0.00026 | $0.00531 |
| Sonnet 5 | $0.00010 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
user-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 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Journey
Trace a specific user's path across multiple sessions — what they did, where they got stuck, and what happened before and after they reported an issue.
When to Use
- "Show me everything user 84721 did this week"
- "A customer says the checkout broke yesterday — trace their sessions"
- "What did this user do before they churned?"
- "Show me the journey of our top 10 enterprise users"
- "Trace [email protected]'s sessions for the last 30 days"
Mental Model
A user journey spans multiple sessions — it's the story of one user across time, not a single session replay. You're looking for patterns: repeated frustrations, feature discovery, upgrade paths, churn signals.
Workflow
Step 1: Find the user
By user ID or email:
fullstory:get_user_profile(userIdentifier="[email protected]")
→ returns user_id, display_name, properties, and recent session metadata
Note the user_id — you'll use it for session searches.
If the user identifier isn't found, try:
- Search by partial match if the tool supports it
- Ask the user for a more specific identifier (full email, exact user ID)
- Try an alternative identifier (email if they gave you an ID, or vice versa)
Step 2: Get session list
fullstory:get_sessions(user_id=user_id, time_range="last_30_days", limit=20)
If the user has many sessions, narrow by time range or look for sessions with notable events (errors, rage clicks).
Step 3: Read session transcripts
For each session, use the session-context agent with a task that varies by what you're looking for:
Bug investigation: "The user reported checkout broke yesterday. Did they visit /checkout? What error occurred? What was the last thing they did before the error?"
Churn investigation: "What frustrations did this user encounter? Did they rage-click, hit errors, or abandon forms? What was their last session before they stopped using the product?"
Power user analysis: "What features does this user engage with most? What's their typical flow? Are there any friction points in their advanced workflows?"
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 · 110 lines · 52 tokens per session scan A c1d011860587
user-journey is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 52 tokens to every session and 1,062 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.