What is session-review?

A tool for reviewing FullStory session recordings, which show how a person used an application. It can inspect screenshots, page changes, event summaries, and the page's component structure.

It helps review a customer-provided session, trace a user's journey, compare two moments on a page, and check whether a UI change behaved correctly.

It helps investigate bugs and unexpected behavior that are difficult to reproduce from a written report alone.

session-review — Skill for Claude Code by reatlat

Install

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.

Any agent

npx skills add reatlat/fullstory-claude-plugin --skill session-review

Clone the repo

git clone --depth 1 https://github.com/reatlat/fullstory-claude-plugin

Made for: Claude Code.

Or install fullstory-reatlat, the plugin that ships this one along with the rest of its 46 skills, 3 agents, 1 MCP server.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-review/github.svg)](https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/session-review)

Your own site

<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.

Your own site · 80×15

<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>

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 953 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00040	$0.00953
Opus 5.5	$0.00016	$0.00381
Sonnet 5.5	$0.00008	$0.00191
Haiku 4.5	$0.00004	$0.00095

Measured 7d ago against content hash 3e0c706369ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 7d 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.

skills/session-review/SKILL.md · 84 lines

How it starts

The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Session review

Start with the session map, narrow to relevant events, and inspect the screen only when needed.

MCP tools

Goal	Tool
Read a transcript without opening a session	`fullstory:review-summary`
Open a session and get its map, first event slice, and `client_id`	`fullstory:review-open`
Read a time window with detail chosen per event kind	`fullstory:review-zoom`
Capture a screenshot, component tree, or both at a timestamp	`fullstory:review-snapshot`
Release the open session's resources	`fullstory:review-close`

For transcript-only questions, use review-summary in an isolated context. It needs neither client_id nor cleanup. For multi-moment visual inspection, delegate to the session-replay agent to keep images out of the main context. If the client cannot load agents, use its isolated-task mechanism with the same workflow.

Workflow

1. Choose the lightest entry point

Use fullstory:review-summary when a transcript answers the question. Otherwise:

fullstory:review-open(session_url="https://app.fullstory.com/ui/<org-id>/session/<device-id>:<session-id>")

Pass the whole URL as session_url. session_id is only the session part and requires device_id. Other supported selectors are trace_id, trace_url, email_address, and user_uid. Use the tool's advertised schema for the selector you have.

The open response contains the session map (span, flow, and event counts), an initial event slice, and client_id. The initial slice is not the complete session.

2. Narrow to key moments

Use the map to locate relevant navigations, clicks, frustration signals, custom events, console errors, and network requests. Read the relevant window:

fullstory:review-zoom(client_id="<id>", t0_ms=<start_ms>, t1_ms=<end_ms>)

Choose detail per event kind using the live tool schema: request full error detail, standard network detail, and summarize unrelated events. Do not invent parameter names for detail controls. Follow returned coverage information rather than treating an omitted event as evidence it never happened.

Read the full file on GitHub · 84 lines

Changes

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.

7d ago Changed · -19 lines · +12 tokens per session 3e0c706369ad
2mo ago First seen · 103 lines · 28 tokens per session scan A 256e1a9736ed

Subscribe to this mod's changes

session-review is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (35 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 953 once invoked, about $0.0002 per session on Opus 5.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.

Analytics and metrics Claude Code Debugging ai-skills claude claude-plugin cursor

session-review next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
session-reviewreatlat/fullstory-claude-plugin	Skill	35	7d ago	MIT	A	40	Claude Code
roblox-performanceTabooHarmony/roblox-brain	Skill	162	23d ago	MIT	A	28	Claude Code
grepai-search-advancedyoanbernabeu/grepai-skills	Skill	20	7d ago	MIT	A	29	Claude Code
grepai-trace-callersyoanbernabeu/grepai-skills	Skill	20	7d ago	MIT	A	28	Claude Code
grepai-trace-graphyoanbernabeu/grepai-skills	Skill	20	7d ago	MIT	A	25	Claude Code
bitrix-loggerbxmaximum/bitrix-framework-skills	Skill	52	2d ago	MIT	A	54	Claude Code, Codex
grepai-mcp-claudeyoanbernabeu/grepai-skills	Skill	20	7d ago	MIT	A	31	Claude Code