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 slack-reportergit 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/slack-reporter)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/slack-reporter"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/slack-reporter/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/slack-reporter"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/slack-reporter.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.00045 | $0.01178 |
| Opus 5 | $0.00023 | $0.00589 |
| Sonnet 5 | $0.00009 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
slack-reporter 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 12d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack Reporter
Format Fullstory findings as clean, scannable Slack messages — key stats, session evidence, and action items. Ready to copy-paste into team channels.
When to Use
- "Send this to #product-engineering on Slack"
- "Format the weekly digest for Slack"
- "Share the frustration analysis with the team"
- "Post an incident update to #incidents"
- "Summarize the experiment results for #growth"
Mental Model
Slack messages are scannable, not readable. Nobody reads paragraphs in Slack. A good Slack report:
- Lead with the headline (what happened, in one sentence)
- Show the numbers (3-5 key stats, max)
- Link to evidence (session URLs, metric URLs)
- End with a clear ask or action item
Workflow
Step 1: Decide what to report
What just happened?
- Investigation completed (frustration analysis, error forensics, funnel analysis)
- Weekly digest ready
- Incident detected
- Experiment concluded
- Anomaly found
Step 2: Extract the headline
One sentence that tells the story:
- "Rage clicks on 'Apply Promo Code' are up 23% week-over-week — 412 users affected, concentrated on mobile checkout."
- "Checkout conversion dropped 4 percentage points after the July 15 deploy. Root cause: API timeout on /api/orders during peak hours."
- "Weekly digest Aug 1-7: product is healthy overall, one new error on /dashboard worth investigating."
Step 3: Format the message
Template:
📊 [Headline]
• 412 users affected (↑23% WoW)
• 73% mobile, concentrated on /checkout
• Avg 6 rage clicks per session before abandonment
🔗 [Session](https://app.fullstory.com/ui/org/session/abc123) | [Metric](https://app.fullstory.com/ui/metric/xyz)
🧵 Root cause: The promo code toast says "applied" but the cart total doesn't update. Users think the promo failed and retry repeatedly.
📋 Recommended: Increase "Apply" button touch target (currently 32px, below 44px minimum) and fix the toast-to-cart-total disconnect. @frontend-team can take this.
cc @product
Step 4: Adapt for context
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.
- 12d ago First seen · 130 lines · 45 tokens per session scan A 3571b7361b3c
slack-reporter is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 29d ago), licensed MIT. It adds 45 tokens to every session and 1,178 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.