What is add-error-tracking?

An integration with Sentry, a service that records application errors and helps teams monitor them. It covers frontend and backend error capture, readable stack traces, user context, breadcrumbs, tags, alerts, and triage workflow.

It is for tracking unhandled errors in Next.js, Azure Functions, or Express applications, uploading source maps, monitoring error rates, configuring alerts, and testing reports.

It makes runtime failures easier to find, understand, group, and prioritize than relying only on local logs.

add-error-tracking — Command by LarouexNonprofitConsulting

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.

Clone the repo

git clone --depth 1 https://github.com/LarouexNonprofitConsulting/larouex-fullstack-plugin

Made for: Claude Code.

Or install larouex-fullstack-builder, the plugin that ships this one along with the rest of its 80 commands.

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/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-tracking/github.svg)](https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-tracking)

Your own site

<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-tracking"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/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/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-tracking"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 128 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.

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.00000	$0.00128
Opus 5.5	$0.00000	$0.00051
Sonnet 5.5	$0.00000	$0.00026
Haiku 4.5	$0.00000	$0.00013

Measured 1mo ago against content hash 6ab3a9fcd1e9, 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 1mo 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

add-error-tracking — 100% identical, 0 lines differ

commands/add-error-tracking.md · 2 lines

What it actually says

Integrate Sentry for comprehensive error tracking and monitoring. Create Sentry project and obtain DSN. Add Sentry SDK to frontend (Next.js) and backend (Azure Functions/Express). Configure source maps upload for readable stack traces. Implement automatic error capture for unhandled exceptions. Add user context (ID, email, username) to error reports. Capture breadcrumbs for user actions leading to errors. Set up custom error tags for categorization. Configure alert rules for critical errors. Implement error rate monitoring and thresholds. Create error triage workflow for team. Reference monitoring-observability-agent for observability setup. Test error tracking in development environment.

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.

1mo ago First seen · 2 lines · 0 tokens per session scan A 6ab3a9fcd1e9

Subscribe to this mod's changes

add-error-tracking is a command published in the GitHub repository LarouexNonprofitConsulting/larouex-fullstack-plugin (8 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 128 tokens. 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-31.

Analytics and metrics Claude Code Debugging azure bootstrap claude-code-plugin fullstack