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-reviewgit 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-review)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/session-review"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-review/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-review"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-review.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.00028 | $0.00943 |
| Opus 5 | $0.00014 | $0.00472 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
session-review 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Review
Review Fullstory sessions to understand what happened — whether diagnosing a customer-reported bug or validating UI changes during development.
When to Use
- User reports a bug and provides a session URL
- Investigating an error or unexpected behavior
- Understanding user flow through the application
- Debugging issues that are hard to reproduce
- Validating UI changes locally after testing
MCP Tools
The tools follow this pattern:
fullstory:session_open → (fullstory:session_view | fullstory:session_diff)* → fullstory:session_close
For a single quick look, call these directly. For multi-moment visual inspection (multiple screenshots/diffs per session, or visual checks across many sessions), delegate to the session-replay agent — screenshots are large and pollute the main context fast.
fullstory:session_open: Passsession_url. Returns event summaries and aclient_id.fullstory:session_view: Screenshot + component tree at a timestamp. Sequential calls with increasing timestamps are faster.fullstory:session_diff: Highlights changes between two timestamps within a page.fullstory:session_close: Always call when done to free resources.
Workflow
1. Open the Session
fullstory:session_open(session_url="https://app.fullstory.com/ui/<org>/session/:<id>")
Returns: event summaries (navigation, clicks, errors, custom events) and client_id.
2. Identify Key Moments
Scan event summaries for:
- Page navigations — entry points into different views
- Click events — user interactions with buttons, links, forms
- Error events — console errors, network failures, renderer errors
- Rage clicks / mouse thrash — signs of UX friction
- Custom events — application-specific telemetry
3. Visual Inspection
At each key moment:
fullstory:session_view(client_id="<...>", page_id="<...>", timestamp=<...>)
Check for:
- Layout correctness (elements positioned properly)
- Content rendering (text, images, icons present)
- Responsive behavior (no overflow, proper sizing)
- Empty/loading states handled
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 · 103 lines · 28 tokens per session scan A 256e1a9736ed
session-review is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 28 tokens to every session and 943 once invoked, about $0.0001 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-performance
Use when profiling Roblox performance or diagnosing FPS, memory, network, mobile, or hot-path problems.
apple-cleanup
Exhaustive engineering hardening of an iOS app. Reviews for Swift 6 compliance, crash risks, App Store rejection risks, and tech debt; builds a surgical plan; dispatches parallel subagents to fix all P0-P2 issues; then pushes an alpha to TestFlight. Use for pre-submission cleanup and code hardening, not design polish.
apple-polish
Design and keynote-readiness craftsmanship review of an iOS app. Evaluates through Jony Ive (visual obsession) and Steve Jobs (demo readiness) perspectives, presents prioritized findings, then orchestrates parallel agents to fix selected issues and push a TestFlight build. Use for design polish, not engineering bugs.
swift6-concurrency
Handle Swift 6 concurrency patterns. Use when encountering Sendable warnings, data race errors, MainActor isolation issues, or framework interop problems (EventKit, Speech, AVFoundation, etc.). Trigger on "Swift 6 error", "Sendable", "data race", "MainActor", "concurrency warning", or "strict concurrency".
asc-build-check
Check the latest CI build status and debug failures using the App Store Connect MCP server. Use when user says "check build", "what broke", "CI status", "build failing", or asks about recent build failures. Also use for signing issues, provisioning profiles, bundle ID capabilities, or Developer Portal queries.
asc-crash-logs
Pull TestFlight crash feedback and full crash logs via the App Store Connect API when Xcode Organizer can't. Use when the user says "pull the crash log", "TestFlight crash", "crash feedback", "get the .ips", or a beta tester reports a crash and you need the stack trace without a device.