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 session-playlistgit 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/session-playlist)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/session-playlist"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-playlist/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/session-playlist"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-playlist.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.00050 | $0.01456 |
| Opus 5 | $0.00025 | $0.00728 |
| Sonnet 5 | $0.00010 | $0.00291 |
| Haiku 4.5 | $0.00005 | $0.00146 |
Grade A, and why
session-playlist 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 10d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Playlist
Curate and share playlists of Fullstory sessions — bundle related sessions with notes, timestamps, and context so your team can watch exactly what matters, in order.
When to Use
- "Bundle these 5 sessions of the checkout bug for the engineering team"
- "Create a playlist of power user sessions for the design review"
- "Share the sessions from the incident investigation"
- "Put together a highlight reel of the new feature adoption"
- "Send the PM 3 sessions showing why users abandon the form"
Mental Model
A playlist is a curated set of sessions with context. Instead of sending 5 raw session links in Slack ("check out these sessions"), you send a playlist with:
- Title: What this playlist shows
- Context: Why these sessions matter
- Per-session notes: What to watch for at which timestamp
- Order: Narrative flow (e.g., "first bug → attempted workaround → successful flow")
Workflow
Step 1: Define the playlist
Ask the user:
- What's the theme? (bug evidence, user research, onboarding review, incident evidence)
- Who's the audience? (engineers, designers, PMs, execs)
- How many sessions? (3-5 is ideal — more than 10 and nobody watches them all)
Step 2: Select sessions
Pull sessions relevant to the theme. Use relevant skills:
frustration-hunter→ sessions with rage clicks or dead clickserror-forensics→ sessions with specific errorssession-search→ sessions matching specific criteriacustomer-360→ sessions from a specific useruser-journey→ sessions across a user's timeline
For each candidate session, open it with session_view to find the key moment — the specific timestamp where the interesting thing happens.
Step 3: Annotate each session
For each session in the playlist:
Session 1: Checkout bug — "Apply Promo" not working
• URL: https://app.fullstory.com/ui/org/session/abc123
• Key moment: 02:34 — user enters promo code "SAVE20"
• Watch for: Toast says "applied" at 02:36, but cart total doesn't change
• User reaction: Clicks "Apply" 5 more times, rage clicks at 02:45, abandons at 03:10
• Device: iPhone 15, Safari
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.
- 10d ago First seen · 149 lines · 50 tokens per session scan A 1b12e789074e
session-playlist is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 28d ago), licensed MIT. It adds 50 tokens to every session and 1,456 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.