What is add-error-tracking?

A guide for adding error tracking to an application through Temps's Sentry-compatible service. Error tracking collects application failures and related details so developers can investigate them; Sentry is a widely used service and SDK for this job.

Use it to configure error reporting for React, Next.js, Vue, Node.js, Python, Go, Rust, Java, PHP, and other supported applications using a Temps DSN, the address that identifies the error-reporting service.

It lets an existing Sentry SDK send errors to Temps by changing the destination address, so the application usually needs little or no new tracking code. It also points developers to platform-specific Sentry setup guides when available.

add-error-tracking — Skill for Claude Code and Codex by gotempsh/temps

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 gotempsh/temps --skill add-error-tracking

Clone the repo

git clone --depth 1 https://github.com/gotempsh/temps

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gotempsh/temps/add-error-tracking/github.svg)](https://agentmods.dev/skills/gotempsh/temps/add-error-tracking)

Your own site

<a href="https://agentmods.dev/skills/gotempsh/temps/add-error-tracking"><img src="https://agentmods.dev/badge/skills/gotempsh/temps/add-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gotempsh/temps/add-error-tracking"><img src="https://agentmods.dev/badge/skills/gotempsh/temps/add-error-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 182 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,544 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

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 4 findings, 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 Privilege Escalation · line 72
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
medium MCP Rug Pull · line 126
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 199
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]
medium MCP Rug Pull · line 283
npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.

Fix: Pin the version: npx @scope/[email protected]

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.

Model	Per session	Once invoked
Fable 5.1	$0.00182	$0.04544
Opus 5.5	$0.00073	$0.01818
Sonnet 5.5	$0.00036	$0.00909
Haiku 4.5	$0.00018	$0.00454

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

Security

Grade A, and why

add-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 28d 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.

skills/add-error-tracking/SKILL.md · 569 lines

How it starts

The opening of the file, as written. The whole thing — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add Error Tracking

Integrate Temps error tracking (Sentry-compatible) into an application. The Temps DSN is a drop-in replacement for a Sentry DSN — use the official Sentry SDK for the user's platform and point it at the Temps DSN via an environment variable.

Prefer Sentry's official per-framework skills when available

Temps is Sentry wire-compatible, so every skill Sentry publishes for their SDKs works against a Temps DSN. If the user's CLI already has one of these installed, route them to it and only substitute the DSN:

User's platform	Sentry skill	Source
Next.js	`/sentry-nextjs-sdk`	`getsentry/sentry-for-ai`
React (Vite, Remix, etc.)	`/sentry-react-sdk`	`getsentry/sentry-for-ai`
Vanilla browser JS	`/sentry-browser-sdk`	`getsentry/sentry-for-ai`
Node.js	`/sentry-node-sdk`	`getsentry/sentry-for-ai`
React Native	`/sentry-react-native-sdk`	`getsentry/sentry-for-ai`
Generic (language-agnostic)	`/sentry-sdk-setup`	`getsentry/sentry-for-ai`

For platforms Sentry has no dedicated skill for (Vue, Svelte, Angular, Python, Go, Rust, Ruby, Java, PHP, .NET, Flutter, etc.), follow the setup in this file directly.

Always set the DSN from an environment variable — never hardcode it. The user will point the env var at their Temps DSN instead of a Sentry DSN.

Detect the platform

Infer the platform from the codebase:

package.json with "next" → Next.js → @sentry/nextjs
package.json with "react" and Vite/Remix/CRA → React → @sentry/react
package.json with "vue" or "nuxt" → Vue → @sentry/vue
package.json with "svelte" or "@sveltejs/kit" → Svelte → @sentry/sveltekit
package.json with "@angular/core" → Angular → @sentry/angular
package.json with "express", "fastify", "@nestjs/core" → Node.js → @sentry/node
package.json with "react-native" or "expo" → React Native → @sentry/react-native
requirements.txt/pyproject.toml with Flask, Django, FastAPI → Python → sentry-sdk
go.mod → Go → github.com/getsentry/sentry-go
Cargo.toml → Rust → sentry
Gemfile with rails → Ruby → sentry-ruby + sentry-rails
pom.xml/build.gradle with Spring → Java → sentry-spring-boot-starter-jakarta
composer.json with laravel/framework or symfony/* → PHP → sentry/sentry
.csproj with Microsoft.AspNetCore.* → .NET → Sentry.AspNetCore
pubspec.yaml with flutter → Flutter → sentry_flutter

Read the full file on GitHub · 569 lines

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.

28d ago Changed · +6 lines 2f72798a1c16
1mo ago First seen · 563 lines · 182 tokens per session scan A 48c687de06a1

Subscribe to this mod's changes

add-error-tracking is a skill published in the GitHub repository gotempsh/temps (846 stars, last pushed today), licensed Apache-2.0. It adds 182 tokens to every session and 4,544 once invoked, about $0.0007 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-08-30.

Analytics and metrics CI and CD DevOps and cloud Frontend deployment-platform docker error-tracking

release-db-config-sync

Compute the remote DB migration + Nacos config diff before a test release — apc release db-config-sync really spawns sync-test-migrations.ts --dry-run (never a stub) and diffs Nacos key dumps, stopping at the write boundary. green(0) no diff · staged(3) pending migrations/missing keys await approval · blocked(1) real…

Prismer-AI/PrismerCloud · 91 tokens

release-preflight

Run the release hard-precondition gate before any tag/OTA — apc release preflight runs the real tier gate (run.ts), version alignment, and prisma regen check, all read-only. green(0) releasable · staged(3) fixable preconditions · blocked(1) tier red/envblocked. No push, no write.

Prismer-AI/PrismerCloud · 76 tokens

add-error-tracking

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Add Error Tracking

Prefer Sentry's official per-framework skills when available

Detect the platform

What this file has done since we first saw it

Other skills, from other repositories

release-db-config-sync

release-preflight

scanning-docker-images-with-trivy

releasing-prod

performing-container-security-scanning-with-trivy

add-ci-area