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 frustration-huntergit 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/frustration-hunter)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/frustration-hunter"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/frustration-hunter/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/frustration-hunter"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/frustration-hunter.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.00067 | $0.00837 |
| Opus 5 | $0.00034 | $0.00418 |
| Sonnet 5 | $0.00013 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
frustration-hunter 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frustration Hunter
Find what's frustrating your users, ranked by impact, grounded in real session evidence.
When to Use
- "What are the biggest frustrations on our site right now?"
- "What's causing friction on the checkout flow for mobile users?"
- "What got worse this week vs last week?"
- "Show me the top rage-clicked elements across our product"
- "Find sessions where users are dead-clicking on the settings page"
Workflow
Step 1: Discover opportunities
Call fullstory:get_opportunities with a time range (default last_7_days). This returns ranked frustration signals — rage clicks, dead clicks, form abandonment, error spikes — each with a user count and page location.
If the user asks about a specific page or flow, scope the opportunities to that area. If they ask "what got worse," use week-over-week comparison (the tool handles this).
Step 2: Get live stats
For the top 3-5 opportunities, call fullstory:get_opportunity_stats on each. This returns:
- Exact user count (not an estimate)
- Device split (mobile vs desktop percentage)
- Page concentration (which pages it happens on)
- Rate-of-change vs prior period (is it getting worse?)
- Frustration rate vs site average
Present the top frustrations as a ranked list:
1. Rage clicks on "Apply Promo Code" — 412 users, 73% mobile, /checkout
2. Dead clicks on cart icon — 287 users, Safari-specific, /products
3. Form abandonment at password field — 218 users, 22s avg dwell before leaving
Step 3: Pull sessions for the worst offenders
Call fullstory:get_sessions_for_opportunity on the top 1-3 opportunities. Get 3-5 sessions each.
For each session, use the session-context agent to read the transcript with a specific task:
- "Did the user's action succeed or fail? What happened after the frustration event?"
- "What element did they rage-click and did anything change on the page after?"
- "Was there an error in the console when this dead click happened?"
Step 4: Synthesize
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 · 76 lines · 67 tokens per session scan A 9d0aa167df55
frustration-hunter is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 67 tokens to every session and 837 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-gui
Use when building Roblox menus, HUDs, shops, notifications, dialogs, or responsive cross-platform UI.
roblox-ui-design
Use for Roblox UI composition, hierarchy, visual systems, style inheritance, accessibility, and design review.
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.
apple-review
Comprehensive Apple-grade review of an iOS app covering design (Apple design leader perspective), engineering (architecture and code quality), compliance (App Store rejection risks), and keynote readiness (product story and demo quality). Use when asked for a full app review, Apple-quality audit, design critique, HIG…
apple-architecture-diagram
Create WWDC-Keynote-ready, self-contained HTML architecture diagrams for Apple platform apps (iOS, macOS, watchOS, tvOS, visionOS). Activates when users ask for app architecture, system design, data flow, module structure, or technical documentation for Apple apps. Produces ultra-beautiful, drill-down capable diagrams…
apple-design
Apple platform design system, iOS 26 & macOS 26 Liquid Glass, design tokens, and accessibility-aware previews. Use when building or reviewing SwiftUI views, defining a theme or design tokens, applying Liquid Glass, organizing asset catalogs, or improving visual consistency. Trigger on "design system", "theme", "design…