sentry-monitoring

Guidance for adding Sentry, a service that records application errors and performance data so developers can investigate production problems. It covers setup across browser, server, and edge runtimes.

In plain words
What is it for?
Use it to initialise Sentry, capture errors, configure performance tracing, upload source maps, track releases, and debug Next.js or Node/Express applications.
Why use it?
It helps connect failures to useful context such as users, releases, source code, and request traces, while avoiding common setup mistakes that hide errors or produce unreadable stack traces.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/monkilabs/opencastle/sentry
Any agent
npx skills add monkilabs/opencastle --skill sentry
Clone the repo
git clone --depth 1 https://github.com/monkilabs/opencastle

Made for: Claude Code, Codex.

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 506 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00054 $0.00506
Opus 5 $0.00027 $0.00253
Sonnet 5 $0.00011 $0.00101
Haiku 4.5 $0.00005 $0.00051

Measured 2d ago against content hash f33b55cde47e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

sentry-monitoring 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 2d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (config.ts), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

src/orchestrator/plugins/sentry/SKILL.md · 28 lines

What it actually says

Sentry Monitoring

Next.js

  • Three separate init files, and the browser one is instrumentation-client.ts — not sentry.client.config.ts — alongside sentry.server.config.ts and sentry.edge.config.ts. npx @sentry/wizard@latest -i nextjs creates all three and patches next.config.ts.
  • Source maps upload only when next.config.ts is wrapped in withSentryConfig() and SENTRY_AUTH_TOKEN (plus SENTRY_ORG / SENTRY_PROJECT) is present at build time, CI included.
  • tunnelRoute: '/monitoring' proxies events through your own origin so ad-blockers stop dropping them.
  • app/global-error.tsx reports nothing by itself — call Sentry.captureException(error) inside it. Wrap server actions in Sentry.withServerActionInstrumentation('name', fn).

Node / Express

import './instrument' must come before every other import in the process. app.use(Sentry.expressErrorHandler()) must be the last error-handling middleware.

Sampling and context

  • tracesSampleRate: 1.0 dev, 0.2–0.5 low-traffic production, 0.05–0.1 high-traffic. Use tracesSampler returning 0 for /health and polling routes, ~0.5 for checkout/auth.
  • Sentry.setUser / setTag / setContext persist for the rest of the session; Sentry.withScope is one-off. Re-throw after captureException when the caller still needs the error.
  • Override issue grouping with event.fingerprint = [...] in beforeSend.
  • Core Web Vitals are captured with no config. Alert thresholds: LCP > 2.5s, CLS > 0.1, INP > 200ms.
  • The DSN is safe to expose client-side. sendDefaultPii: true captures IP, user agent, and authenticated user.

Docs: https://docs.sentry.io/

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2d ago First seen · 28 lines · 54 tokens per session scan A f33b55cde47e

Subscribe to this mod's changes

sentry-monitoring is a skill published in the GitHub repository monkilabs/opencastle (61 stars, last pushed 4d ago), licensed MIT. It adds 54 tokens to every session and 506 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.

Related

Other skills, from other repositories

product-architect

Complete product development system with 64 agents and 35 frameworks. Use when the user wants to build a product, write a PRD, plan an MVP or roadmap, design an app, research a market or check whether a feature already exists or is novel, do competitive analysis, run a security audit, build a financial model, plan…

ankitjha67/product-architect · 211 tokens

codex-delegation

Use when a coding task would benefit from delegating work to Codex in the background — a deep independent second opinion, security or architecture analysis, or a parallel implementation running while the session continues. Lets Claude drive the codex companion itself (task, review, status --wait, result) without the…

zebbern/agent-collab · 74 tokens

cursor-delegation

Use when a coding task would benefit from delegating work to Cursor in the background — fast parallel implementation, scaffolding, or an everyday review running while the session continues. Lets Claude drive the cursor companion itself (task, review, status --wait, result) without the user typing /cursor: commands.

zebbern/agent-collab · 66 tokens

cursor-cli-runtime

Internal helper contract for calling the cursor-companion runtime from Claude Code.

zebbern/agent-collab · 17 tokens

cursor-prompting

Internal guidance for composing cursor-agent prompts and picking models for coding, review, diagnosis, and research tasks inside the Cursor Claude Code plugin.

zebbern/agent-collab · 31 tokens

goal-runner

Use when the user asks to advance, continue, or work on the project's long-horizon goal (or to set one up) — the policy for goal-driven increments driven through the goal companion, one increment at a time, delegated via the codex/cursor delegation skills, honestly recorded.

zebbern/agent-collab · 62 tokens