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 weekly-digestgit 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/weekly-digest)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/weekly-digest"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/weekly-digest/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/weekly-digest"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/weekly-digest.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.00053 | $0.01028 |
| Opus 5 | $0.00026 | $0.00514 |
| Sonnet 5 | $0.00011 | $0.00206 |
| Haiku 4.5 | $0.00005 | $0.00103 |
Grade A, and why
weekly-digest 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Weekly Digest
A structured weekly summary of what changed in your product: frustrations, errors, conversion trends, and notable shifts.
When to Use
- "What changed this week vs last week?"
- "Give me a weekly recap of product health"
- "What should I put in the weekly product update?"
- "Anything trending sharply up or down this week?"
- "What new errors appeared this week?"
Mental Model
The digest compares two time periods — typically "this week" vs "last week" — across four dimensions:
- Frustration signals — rage clicks, dead clicks, form abandonment
- Errors — console errors, network failures, crashes
- Conversion — key funnel metrics
- Traffic — overall page views and session count
The output is a structured report, not a deep investigation. Flag what's worth digging into; the user can then invoke the specific skill (frustration-hunter, error-forensics, funnel-doctor) for the things that matter.
Workflow
Step 1: Frustrations
Call fullstory:get_opportunities(time_range="last_7_days"). Compare to prior 7 days.
For each opportunity, call fullstory:get_opportunity_stats. Flag anything with:
- User count increase >20% week-over-week
- New signal that didn't exist last week
- Frustration rate significantly above site average
Present top 3-5 as a ranked list with week-over-week change.
Step 2: Errors
Build a metric for errors (console errors, network failures):
fullstory:build_metric(
query="console errors and network failures",
output_type="trend"
)
fullstory:compute_metric(metric_id, time_range="last_14_days")
Flag:
- Errors that started this week (zero last week, non-zero now)
- Errors with >50% increase week-over-week
- Most frequent error overall
Step 3: Conversion
Pick 2-3 key funnels (checkout, signup, onboarding). If they don't exist in the account, ask the user which funnels matter. Build a trend metric for each:
fullstory:compute_metric(funnel_metric_id, time_range="last_14_days")
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 · 118 lines · 53 tokens per session scan A a1600c8d7f8b
weekly-digest is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 28d ago), licensed MIT. It adds 53 tokens to every session and 1,028 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.