Agent skill · marketing growth · jeremylongshore
sentry-cost-tuning
Optimize Sentry costs, reduce event volume, and manage quota spend.
Why this skill is useful
Provides specific Sentry API commands and configuration patterns for cost optimization that the AI wouldn't reliably generate on its own.
What it needs
Requires @sentry/browser, @sentry/node installed locally. Requires sentry account access. About 9k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Sentry Cost Tuning Overview Reduce Sentry spend by 60-95% through SDK-level sampling, server-side inbound filters, beforeSend event dropping, and quota management — without losing visibility into production errors that matter. Prerequisites Active Sentry account with org:read and project:read scopes on an auth token Access to the project's Sentry.init() configuration (typically sentry.client.config.ts or instrument.ts) Current plan tier identified: Developer (free, 5K errors/mo), Team ($26/mo, 50K errors + 100K transactions), or Business ($80/mo, 100K errors + 500K transactions) SENTRYAUTHTOKEN and SENTRYORG environment variables set for API calls @sentry/node >= 8.0 or @sentry/browser >= 8.0 installed Instructions Step 1 — Audit Current Usage via the Stats API Query the Sentry Usage Stats API to understand where volume comes from before making changes. This endpoint returns event counts grouped by category over any time period. Record the baseline numbers. You need these to measure savings after optimization. Step 2 — Configure Error Sampling with sampleRate The sampleRate option in Sentry.init() controls the percentage of error events sent to Sentry. Setting it to 0.1 means only 10% of errors are sent, yielding a 90% cost reduction on the error category. Trade-off: Low-frequency errors (< 10 occurrences/day) may be missed entirely. Mitigate this by using beforeSend to always send errors with specific severity or tags rather than relying on blanket sampling. Step 3 — Configure Performance Sampling with tracesSampleRate and tracesSampler Performance monitoring (transactions/spans) is typically the largest cost driver. A tracesSampleRate of 0.05 sends only 5% of traces, cutting performance costs by 95%. The tracesSampler function receives a samplingContext with the transaction name (usually the route) and attributes. Return a number between 0 (drop) and 1 (always send), or true/false. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/sentry-cost-tuning