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 customer-360git 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/customer-360)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/customer-360"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/customer-360/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/customer-360"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/customer-360.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.01172 |
| Opus 5 | $0.00027 | $0.00586 |
| Sonnet 5 | $0.00011 | $0.00234 |
| Haiku 4.5 | $0.00005 | $0.00117 |
Grade A, and why
customer-360 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 12d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Customer 360
Complete view of a single customer — all their sessions, key actions, frustration events, purchases, and engagement history in one place.
When to Use
- "Show me everything about customer [email protected]"
- "What's the history of user 84721? Support escalated their ticket."
- "Sales wants to know if Acme Corp has been evaluating our product — check their sessions."
- "This enterprise customer is threatening to churn — what's their experience been?"
- "Onboard a new CSM — give them the full picture of this account."
Mental Model
A Customer 360 is a structured snapshot of one user across all dimensions available in Fullstory:
- Identity: Who they are (email, plan, role, account)
- Engagement: How often they use the product, what features
- Success: Did they achieve their goals (conversions, completions)?
- Friction: What frustrated them (errors, rage clicks, dead clicks)?
- Trajectory: Getting better or worse over time?
Workflow
Step 1: Look up the customer
Start with whatever identifier you have:
fullstory:get_user_profile(userIdentifier="[email protected]")
→ returns user_id, display_name, email, plan, role, first_seen, last_seen, total_sessions
If the lookup returns nothing, try alternative identifiers or ask the user for a more specific one.
Step 2: Get session history
fullstory:get_sessions(user_id, time_range="last_90_days", limit=50)
If many sessions, sample strategically:
- First 5 sessions (onboarding experience)
- Last 5 sessions (current state)
- Any sessions with errors or high frustration signals
Step 3: Identify key events
Use session-context agent to scan each sampled session for:
- Conversions: purchases, signups, upgrades
- Friction: errors, rage clicks, dead clicks, form abandonment
- Feature usage: which features did they use? power user or casual?
- Support indicators: visited help pages, searched docs, contacted support
Step 4: Check for frustration patterns
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.
- 12d ago First seen · 126 lines · 54 tokens per session scan A bd3fc3a16987
customer-360 is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 1,172 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-security
Use when auditing Roblox code for exploit vectors, authority models, remotes, economy, and DataStore flows.