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-searchgit 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-search)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/session-search"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-search/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-search"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/session-search.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.00044 | $0.00929 |
| Opus 5 | $0.00022 | $0.00464 |
| Sonnet 5 | $0.00009 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
session-search 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Search
Find sessions by searching across user properties, device, browser, custom events, and pages — without needing a metric or segment first.
When to Use
- "Find sessions where users on Safari mobile visited /checkout"
- "Show me sessions from enterprise users who saw an error"
- "Find the session for user ID 84721 from yesterday"
- "Show me sessions where custom event 'trial_started' fired"
- "Find sessions from users in Germany who visited the pricing page"
Mental Model
Session search is for targeted lookups when you know who or what you're looking for. It's different from metrics (which aggregate across many users) and opportunities (which rank by frustration). Session search is a point query: "find me these specific sessions."
Workflow
Step 1: Clarify the search criteria
What does the user know? Common search axes:
| Criterion | Tool |
|---|---|
| Specific user ID or email | fullstory:get_user_profile → sessions |
| Device type or browser | fullstory:get_sessions with device/browser filters |
| Page URL | fullstory:get_sessions with page filter |
| Custom event | fullstory:get_sessions with event filter |
| User property (plan, role, country) | Build segment → fullstory:get_sessions(segment_id) |
| Time range | Always specify — narrow is faster |
Step 2: Execute the search
By user ID or email:
fullstory:get_user_profile(userIdentifier="[email protected]")
→ returns user's recent sessions with device_id and session_id
→ load each session through session-context agent
By device/browser/page:
fullstory:get_sessions(
device="mobile",
browser="safari",
page="/checkout",
time_range="last_7_days",
limit=5
)
By user property (plan, role, country):
fullstory:build_segment("users on enterprise plan in Germany")
fullstory:get_sessions(segment_id=segment_id, limit=5)
By custom event:
fullstory:get_sessions(
event="trial_started",
time_range="last_30_days",
limit=5
)
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 · 107 lines · 44 tokens per session scan A a9cdc2842d8d
session-search is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 28d ago), licensed MIT. It adds 44 tokens to every session and 929 once invoked, about $0.0002 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.