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/LarouexNonprofitConsulting/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/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-boundary)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-boundary"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-boundary/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/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-boundary"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-error-boundary.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.00117 |
| Opus 5.5 | $0.00000 | $0.00047 |
| Sonnet 5.5 | $0.00000 | $0.00023 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
add-error-boundary 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-error-boundary — 100% identical, 0 lines differ
What it actually says
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: page-level, component-level, layout-level. Preserve error context for debugging. Add development vs production error displays. Implement automatic error recovery attempts. Create error reporting UI for users to submit details. Add error boundary for async components with Suspense. Reference frontend-development-agent for React patterns. Test error handling with intentional errors in development.
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 143254b522f4
add-error-boundary 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 117 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.
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…
review-code
Review all uncommitted changes in the current working directory using code-review-agent. Analyze code quality, security vulnerabilities, performance issues, accessibility compliance, and adherence to Next.js 15 and React 18+ best practices. Check TypeScript strict mode compliance, proper Server/Client component usage…
review-component
Review a specific React component file using code-review-agent and frontend-development-agent. Analyze component architecture, proper Server vs Client component usage, prop types, hooks patterns (useState, useEffect, useCallback, useMemo), accessibility attributes (ARIA labels, semantic HTML, keyboard navigation)…
review-performance
Analyze application performance using code-review-agent and monitoring-observability-agent. Check Core Web Vitals (LCP < 2.5s, FID < 100ms, CLS < 0.1), bundle size analysis, image optimization (next/image, WebP format), font optimization (next/font), code splitting and lazy loading, caching strategies…
scaffold-nextjs
Scaffold a basic Next.js 15 project with modern best practices.