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 webhook-healthgit 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/webhook-health)<a href="https://agentmods.dev/skills/reatlat/fullstory-claude-plugin/webhook-health"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/webhook-health/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/webhook-health"><img src="https://agentmods.dev/badge/skills/reatlat/fullstory-claude-plugin/webhook-health.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 20 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
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.00038 | $0.01228 |
| Opus 5 | $0.00019 | $0.00614 |
| Sonnet 5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
webhook-health 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Webhook Health
Monitor FullStory webhook delivery — is data flowing to your integrations, are webhooks failing, and are your downstream systems healthy?
When to Use
- "Are our FullStory webhooks delivering successfully?"
- "Why didn't sessions show up in our data warehouse?"
- "Check webhook delivery since the configuration change"
- "Which webhook endpoints are failing?"
- "Monitor webhook health for the Slack and Jira integrations"
Mental Model
FullStory can send session data, events, and alerts to external systems via webhooks. If webhooks fail, data stops flowing — your data warehouse misses sessions, your Slack channel stops getting alerts, your Jira integration stops creating tickets.
Webhook monitoring has two sides:
- Delivery: Did FullStory successfully deliver the webhook? (HTTP 2xx response)
- Processing: Did your downstream system correctly process the payload? (business logic failures)
FullStory can tell you about delivery. Processing failures need to be checked in the downstream system.
Workflow
Step 1: Check webhook configuration
Verify what's configured. Webhooks are typically set up in Fullstory's integration settings or API. Ask the user:
- "What webhook endpoints do you have configured?"
- "What events trigger them? (new session, new event, segment export, etc.)"
- "When were they last known to be working?"
If the user isn't sure, direct them to: Fullstory → Settings → Integrations → Webhooks
Step 2: Check for delivery failures
Build a metric for webhook-related errors or check session data for failed webhook deliveries:
fullstory:build_metric(
query="custom events related to webhook failures",
output_type="single_number"
)
Or check if the data pipeline has gaps:
fullstory:build_metric(query="sessions created", output_type="trend")
fullstory:compute_metric(metric_id)
→ compare to your data warehouse: do the session counts match?
Step 3: Verify integration health
For each downstream integration (Slack, Jira, data warehouse, Snowflake), verify data flow:
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 · 120 lines · 38 tokens per session scan A 8b55f19ca41a
webhook-health is a skill published in the GitHub repository reatlat/fullstory-claude-plugin (62 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,228 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
n8n-architect
Use when the user explicitly wants to create, edit, validate, sync, or troubleshoot n8n workflows, asks about n8n nodes or automation, or wants to use n8n-as-code in the current context root.
roblox-cloud
Use for Roblox Open Cloud APIs, API keys, OAuth 2.0, webhooks, scopes, token lifecycle, or in-experience HttpService calls.
networking
Modern Swift networking with URLSession and async/await — typed requests, Codable decoding, HTTP status & error handling, retry with backoff, offline/connectivity handling, and a Sendable API client. Use when calling a REST/JSON API, building an API client/service layer, decoding responses, handling network errors or…
cloudkit-sync
Sync SwiftData / Core Data across a user's devices with CloudKit, plus CKShare collaboration and conflict handling. Use when adding iCloud sync, "sync across devices", SwiftData + CloudKit, NSPersistentCloudKitContainer, sharing records between users, or debugging why data isn't syncing. Trigger on "CloudKit", "iCloud…
add-request-protection
Deprecated: use the arcjet skill instead. Adds security protection to a server-side route or endpoint — rate limiting, bot detection, email validation, and abuse prevention.
bitrix-sale
Covers Sale module — API choice (D7 object model vs ORM vs CSale), FUSER, Basket, Order create/update, properties, statuses and events, payments, delivery/shipments, discounts and coupons, reservation/deduction, permissions, buyer accounts. Applied for cart/checkout, order lifecycle, pay/ship integration, and order…