error-handling-reviewer

error-handling-reviewer is an agent for Claude Code from OutSystems/outsystems-mcp. It costs 24 tokens per session (1,717 once invoked), scanned A, original, MIT.

A code review agent that looks for errors which are swallowed, hidden, or passed through the wrong part of a program.

In plain words
What is it for?
Use it to inspect changed code for discarded exceptions, silent failures, overly broad handling, and broken error propagation.
Why use it?
It helps prevent failures from becoming silent or being replaced by fallback behavior that conceals the real problem.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the outsystems plugin — 2 skills, 1 command, 4 agents shipped together

Good fit Use it to inspect changed code for discarded exceptions, silent failures, overly…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/outsystems/outsystems-mcp/error-handling-reviewer
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/OutSystems/outsystems-mcp

Made for: Claude Code.

Or install outsystems, the plugin that ships this one along with the rest of its 2 skills, 1 command, 4 agents.

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-handling-reviewer

README.md
[![agentmods](https://agentmods.dev/badge/agents/outsystems/outsystems-mcp/error-handling-reviewer.svg)](https://agentmods.dev/agents/outsystems/outsystems-mcp/error-handling-reviewer)
Your own site
<a href="https://agentmods.dev/agents/outsystems/outsystems-mcp/error-handling-reviewer"><img src="https://agentmods.dev/badge/agents/outsystems/outsystems-mcp/error-handling-reviewer.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,717 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.01717
Opus 5 $0.00012 $0.00859
Sonnet 5 $0.00005 $0.00343
Haiku 4.5 $0.00002 $0.00172

Measured 3d ago against content hash 531b899ae199, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

error-handling-reviewer 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 3d 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.

.claude/agents/error-handling-reviewer.md · 138 lines

How it starts

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

Error Handling Reviewer Agent

Purpose

Hunt for swallowed errors, silent failures, and broken error propagation chains.

Scope

  • Swallowed errors — catch/except blocks that discard error information
  • Silent failures — operations that fail without logging, notification, or propagation
  • Broken error propagation — errors caught at the wrong level, preventing proper handling upstream
  • Incorrect error handling — catching too broadly, wrong error types, or fallback behavior that masks real problems

What NOT to flag

  • Missing try-catch blocks on code that doesn't need them — do NOT suggest adding error handling "just in case." Only flag EXISTING error handling that is wrong or MISSING error handling where a failure WILL occur and be silently lost.
  • Logging improvements — do NOT suggest better log messages, additional context in logs, or different log levels unless the current logging actively hides an error.
  • Error message quality — do NOT flag unclear error messages or missing user-facing feedback. Focus only on whether errors are propagated, not how they're presented.
  • Defensive coding patterns — do NOT suggest adding null checks, input validation, or guard clauses. That's a different concern.

Inputs

You will receive:

  • Base SHA: The base commit to diff against

The repository is already checked out at the correct HEAD commit. Run git diff <base_sha>...HEAD yourself to get the diff. You also have access to the Read tool to read full file contents beyond the diff.

Instructions

Step 1: Identify All Error Handling Code in the Diff

Locate every place in the changed code where errors are handled or where execution can exit early on failure:

  • try-catch / try-except blocks
  • if err != nil patterns (Go)
  • Result/Option handling (Rust)
  • .catch() handlers (JavaScript/TypeScript)
  • Error callbacks and event handlers
  • Conditional branches that handle error/failure states
  • Early exits from loops (break, return, continue on error) — especially in loops that produce side effects before the exit point

Read the full file on GitHub · 138 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.

  1. 3d ago First seen · 138 lines · 24 tokens per session scan A 531b899ae199

Subscribe to this mod's changes

error-handling-reviewer is an agent published in the GitHub repository OutSystems/outsystems-mcp (25 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 1,717 once invoked, about $0.0001 per session on Opus 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-04.

Related

Other agents, from other repositories

performance-auditor

Use proactively on performance-sensitive changes. Flags O(n²) paths, N+1 queries, unnecessary re-renders, and hot-path waste. Reports with file:line refs and estimated impact. Does not fix.

onlygian/G-Forge · 48 tokens

streaming-reviewer

Streaming / event-driven pre-implementation reviewer. Outputs threat model TM-{slug}.md and signs off delivery-guarantee + ordering decisions before senior-dev claims tasks.

avelikiy/great_cto · 38 tokens

challenger

Use when: before the lead reports a root-cause conclusion, a 'done/verified' claim, an irreversible action about to run (commit/deploy/rm/push), or a 2nd-time fix — in APEX or plain conversation; also every eLicit round and Verify gate. Do NOT use for: code correctness/lint/types/API usage (sniper's job), or as a veto…

fusengine/agents · 92 tokens

fec-performance-optimizer

Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…

bovinphang/frontend-craft · 0 tokens

fec-ui-checker

Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…

bovinphang/frontend-craft · 0 tokens

bug-detector

Detects correctness bugs, logic errors, edge cases, API misuse, and error handling issues in code changes.

liatrio-labs/claude-code-gauntlet · 25 tokens