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.
git clone --depth 1 https://github.com/Ashikparvez89/larouex-fullstack-pluginWrote 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.
[](https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/add-error-tracking)<a href="https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/add-error-tracking"><img src="https://agentmods.dev/badge/commands/ashikparvez89/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.
<a href="https://agentmods.dev/commands/ashikparvez89/larouex-fullstack-plugin/add-error-tracking"><img src="https://agentmods.dev/badge/commands/ashikparvez89/larouex-fullstack-plugin/add-error-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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 |
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.
This is a copy
100% identical to add-error-tracking — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
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
add-error-tracking is a command published in the GitHub repository Ashikparvez89/larouex-fullstack-plugin (3 stars, last pushed 8d 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. It is 100% identical to add-error-tracking, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
add-error-boundary
Implement React error boundaries throughout the application. Create error boundary component with componentDidCatch lifecycle. Add fallback UI with friendly error message and retry button. Log errors to monitoring service (Sentry, Azure Monitor) with stack traces. Implement granular boundaries for different sections…
add-error-tracking
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…
deploy-azure-production
Deploy to Azure production with mandatory review gate and comprehensive validation.
deploy-railway-production
Deploy to Railway production environment with mandatory review gate and validation.
add-auth
Implement authentication system with comprehensive user management.
audit-accessibility
Audit the project for WCAG 2.1 AA accessibility compliance.