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 heatmap-generatorgit 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/heatmap-generator)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/heatmap-generator"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/heatmap-generator/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/heatmap-generator"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/heatmap-generator.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.00056 | $0.01367 |
| Opus 5 | $0.00028 | $0.00683 |
| Sonnet 5 | $0.00011 | $0.00273 |
| Haiku 4.5 | $0.00006 | $0.00137 |
Grade A, and why
heatmap-generator 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Heatmap Generator
Generate interaction heatmaps from real session data — click density, tap zones, rage click hotspots, and dead click dead zones. No visual rendering (Fullstory doesn't expose pixel coordinates natively) — instead, element-level aggregation showing which elements get the most and least interaction.
When to Use
- "What do users click on most on the homepage?"
- "Show me a click map of the pricing page"
- "Are users clicking non-interactive elements?"
- "Where should we place the CTA on the landing page?"
- "Which elements are being ignored?"
- "Compare click patterns between new and returning users"
Mental Model
A heatmap visualizes interaction density. Hot zones = elements users interact with a lot. Cold zones = elements users ignore (or can't find). Rage click zones = elements users click repeatedly — often non-interactive elements that look clickable.
Fullstory doesn't expose cursor coordinates through the MCP, so you can't render a pixel-accurate heatmap. Instead, you generate an element-level interaction map — showing which DOM elements get clicked, how often, and in what pattern.
Workflow
Step 1: Choose the page
Which page? Landing page, pricing page, product page, checkout.
Specify page: /pricing, /landing, /products/*
Step 2: Aggregate clicks by element
Build a metric for click events on the page:
fullstory:build_metric(
query="click events on /pricing by element",
output_type="top_n"
)
fullstory:compute_metric(metric_id)
This returns the most-clicked elements, ranked by click count.
Step 3: Identify interaction patterns
Hot elements (high click count):
- Are these the intended CTAs? Good — users are finding them.
- Are these non-interactive elements? Bad — users think they're clickable but they're not (dead click risk).
Cold elements (low/no clicks):
- Is the primary CTA here? Bad — users aren't finding it.
- Is this decorative or secondary content? Good — expected.
Rage click zones (repeated clicks on same element):
fullstory:get_opportunities → filter by page → look for rage click signals
→ "Rage clicks on 'Apply Promo' button: 412 users, concentrated on /checkout"
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 · 136 lines · 56 tokens per session scan A 97b16e1b3e6c
heatmap-generator is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 28d ago), licensed MIT. It adds 56 tokens to every session and 1,367 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.