error-tracking

error-tracking is a skill for Claude Code, Codex from aj-geddes/useful-ai-prompts. It costs 39 tokens per session (464 once invoked), scanned A, original, MIT.

A guide to monitoring application errors with Sentry, a service that collects and organizes exceptions and performance problems. It covers release tracking, source maps, user impact, and custom error context.

In plain words
What is it for?
Use it to capture exceptions, monitor application stability, track releases, detect performance problems, and add context to reported errors.
Why use it?
It gives developers a way to find and investigate failures occurring in production. It can connect errors to releases and help identify which users or performance issues are affected.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to capture exceptions, monitor application stability, track releases, detect performance problems, and add context to reported errors.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aj-geddes/useful-ai-prompts/error-tracking
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.

Any agent
npx skills add aj-geddes/useful-ai-prompts --skill error-tracking
Clone the repo
git clone --depth 1 https://github.com/aj-geddes/useful-ai-prompts

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for error-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/error-tracking/github.svg)](https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/error-tracking)
Your own site
<a href="https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/error-tracking"><img src="https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/error-tracking/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.

agentmods 80×15 button for error-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/aj-geddes/useful-ai-prompts/error-tracking"><img src="https://agentmods.dev/badge/skills/aj-geddes/useful-ai-prompts/error-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 39 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • Socket warn 16 Sept 2026
  • Snyk pass 16 Sept 2026
How audits are shown
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.1 $0.00039 $0.00464
Opus 5.5 $0.00016 $0.00186
Sonnet 5.5 $0.00008 $0.00093
Haiku 4.5 $0.00004 $0.00046

Measured 2mo ago against content hash 370d6500c86f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

error-tracking 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 2mo ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/validate-api.sh), 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.

skills/error-tracking/SKILL.md · 76 lines

What it actually says

Error Tracking

Table of Contents

Overview

Set up comprehensive error tracking with Sentry to automatically capture, report, and analyze exceptions, performance issues, and application stability.

When to Use

  • Production error monitoring
  • Automatic exception capture
  • Release tracking
  • Performance issue detection
  • User impact analysis

Quick Start

Minimal working example:

npm install -g @sentry/cli
npm install @sentry/node @sentry/tracing
sentry init -d

Reference Guides

Detailed implementations in the references/ directory:

Guide Contents
Sentry Setup Sentry Setup, Node.js Sentry Integration
Express Middleware Integration Express Middleware Integration
Python Sentry Integration Python Sentry Integration
Source Maps and Release Management Source Maps and Release Management, CI/CD Release Creation
Custom Error Context Custom Error Context
Performance Monitoring Performance Monitoring

Best Practices

✅ DO

  • Set up source maps for production
  • Configure appropriate sample rates
  • Track releases and deployments
  • Filter sensitive information
  • Add meaningful context to errors
  • Use breadcrumbs for debugging
  • Set user information
  • Review error patterns regularly

❌ DON'T

  • Send 100% of errors in production
  • Include passwords in context
  • Ignore configuration for environment
  • Skip source map uploads
  • Log personally identifiable information
  • Use without proper filtering
  • Disable tracking in production
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. 2mo ago First seen · 76 lines · 39 tokens per session scan A 370d6500c86f

Subscribe to this mod's changes

error-tracking is a skill published in the GitHub repository aj-geddes/useful-ai-prompts (376 stars, last pushed 8mo ago), licensed MIT. It adds 39 tokens to every session and 464 once invoked, about $0.0002 per session on Opus 5.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-09-03.

Related

error-tracking compared with skills from other repositories

error-tracking next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
error-trackingaj-geddes/useful-ai-promptsSkill3768mo agoMITA39Claude Code, Codex
systematic-debuggingopen-metadata/OpenMetadataSkill16kyesterdayApache-2.0A37Claude Code
log-error-digestzebbern/claude-code-guideSkill4.7k3d agoMITA71Claude Code, Codex
cwv-optimizeradobe/skillsSkill319yesterdayApache-2.0A112Claude Code
ci-fixersipyourdrink-ltd/bernsteinSkill1.2kyesterdayApache-2.0A15Claude Code, Codex
incident-response-incident-responsermyndharis/antigravity-skillsSkill1.9k23d agoMITA36Claude Code
triaging-web-analytics-supportPostHog/posthogSkill41kyesterdaynoneA151Claude Code, Codex