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 scroll-depth-analyzergit 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/scroll-depth-analyzer)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/scroll-depth-analyzer"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/scroll-depth-analyzer/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/scroll-depth-analyzer"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/scroll-depth-analyzer.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.00043 | $0.01497 |
| Opus 5 | $0.00022 | $0.00749 |
| Sonnet 5 | $0.00009 | $0.00299 |
| Haiku 4.5 | $0.00004 | $0.00150 |
Grade A, and why
scroll-depth-analyzer 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scroll Depth Analyzer
Measure how far users scroll on your pages — where they stop, what they see, and whether your key content is actually being viewed.
When to Use
- "Are users scrolling past the fold on the landing page?"
- "Do users reach the CTA at the bottom of the pricing page?"
- "Where do users stop reading on the blog post?"
- "Is the important content on /features actually being seen?"
- "Compare scroll depth between new and returning visitors"
- "Did the new page layout improve scroll depth?"
Mental Model
Users don't read every word. They scan and scroll. The question is: do they scroll far enough to see the important stuff?
Scroll depth is measured in percentage of the page:
- 25% — User saw the hero/header
- 50% — User saw the first section of content
- 75% — User saw most of the page
- 100% — User reached the footer
The "fold" (visible area without scrolling) varies by device — it's roughly 600-800px on desktop, 500-600px on mobile. Content above the fold gets nearly 100% visibility. Content at 75% scroll depth might only be seen by 30% of users.
Workflow
Step 1: Choose the page
Which page does the user want to analyze? Typically:
- Landing pages (are users reading the pitch?)
- Pricing pages (do users see all tiers?)
- Blog posts (are users reading to the end?)
- Product pages (are users seeing the specs?)
- Checkout pages (are users seeing the full form?)
Step 2: Build scroll depth metrics
Fullstory doesn't have a native scroll depth metric, so build it from page view and time-spent data:
fullstory:build_metric(
query="users who viewed /pricing",
output_type="single_number"
) → total visitors
fullstory:build_metric(
query="users who spent >30 seconds on /pricing",
output_type="single_number"
) → engaged visitors (read beyond the fold)
fullstory:build_metric(
query="users who spent >60 seconds on /pricing",
output_type="single_number"
) → deep readers (read most of the page)
Time on page is a proxy for scroll depth — longer time = more scrolling.
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 · 149 lines · 43 tokens per session scan A 1c21249928ea
scroll-depth-analyzer is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 27d ago), licensed MIT. It adds 43 tokens to every session and 1,497 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-data
Use when implementing player data persistence with DataStore, session ownership, schemas, migrations, or save and load flows.
roblox-networking
Use when validating RemoteEvent or RemoteFunction arguments, adding rate limits, designing server-authoritative systems, or preventing exploits.